Vultr, Los Angeles vps evaluation sharing

The machines in the big factory are stable, so Xiaobai suggests using the machines in the big factory. There are not so many bad things to worry about. In addition, the factory is very friendly to new users. For example, Vultr will give new users $50 or $100. Of course, there is a time limit for this gift, which should be used up within 30 days.

This article is to evaluate the vps in Los Angeles on the west coast of Vultr. Of course, Motao selected the high-frequency series, which is not different from the ordinary ones. It costs only $1 a month. If you are a new user and have free money, you can choose any machine. Want to know How about vultr How about good children's shoes? Come here quickly.

1. Official website

website: https://www.vultr.com/zh/

2. New user registration and bonus acquisition

See the tutorial here: https://imotao.com/5782.html

3. Evaluate the machine configuration

The evaluation machine selects the high-frequency version, which is the package scheme in the third line.

4. System information

The CPU has been virtualized, and the model cannot be seen, but the frequency is high. Disk IO is very powerful. The uplink port should be 10G, and the downlink port should be G.

5. Miscellaneous Tests

Media test

For domestic speed measurement and evening peak test, the bandwidth port is still very large, with downlink G port and uplink 10G port.

Foreign test

 ## CDN Speedtest CacheFly :  85.62 MiB/s |  684.93 Mbps  | ping   0.304ms Gdrive   :  30.82 MiB/s |  246.53 Mbps  | ping   0.347ms ## North America Speedtest Softlayer, Washington, USA :  10.87 MiB/s |   86.93 Mbps  | ping  60.875ms SoftLayer, San Jose, USA   :  48.25 MiB/s |  385.98 Mbps  | ping  39.669ms SoftLayer, Dallas, USA     :       0 B/s |      N/A       | ping error! Vultr, New Jersey, USA     :  30.96 MiB/s |  247.68 Mbps  | ping  74.829ms Vultr, Seattle, USA        :  79.05 MiB/s |  632.41 Mbps  | ping  27.093ms Vultr, Dallas, USA         :  73.96 MiB/s |  591.72 Mbps  | ping  29.413ms Vultr, Los Angeles, USA    : 312.50 MiB/s | 2500.00 Mbps  | ping   0.324ms Ramnode, New York, USA     :  38.15 MiB/s |  305.18 Mbps  | ping  56.101ms Ramnode, Atlanta, USA      :  44.09 MiB/s |  352.72 Mbps  | ping  43.637ms OVH, Beauharnois, Canada   :       0 B/s |      N/A       | ping  67.668ms ## Europe Speedtest Vultr, London, UK            :  15.03 MiB/s |  120.27 Mbps  | ping 138.395ms LeaseWeb, Frankfurt, Germany :  13.03 MiB/s |  104.24 Mbps  | ping 142.840ms Hetzner, Germany             :   9.88 MiB/s |   79.02 Mbps  | ping 145.487ms Ramnode, Alblasserdam, NL    :  14.12 MiB/s |  112.99 Mbps  | ping 141.944ms Vultr, Amsterdam, NL         :  11.75 MiB/s |   94.04 Mbps  | ping 145.919ms EDIS, Stockholm, Sweden      :     200 B/s |      N/A       | ping 157.361ms OVH, Roubaix, France         :   8.13 MiB/s |   65.06 Mbps  | ping 135.924ms Online, France               :  12.86 MiB/s |  102.85 Mbps  | ping 139.878ms Prometeus, Milan, Italy      :     355 B/s |      N/A       | ping 153.319ms ## Exotic Speedtest Sydney, Australia     :  10.87 MiB/s |   86.96 Mbps  | ping 155.653ms Lagoon, New Caledonia :     197 B/s |      N/A       | ping 169.621ms Hosteasy, Moldova     :   3.29 MiB/s |   26.30 Mbps  | ping 179.186ms Prima, Argentina      : 590.16 KiB/s |    4.61 Mbps  | ping error! ## Asia Speedtest SoftLayer, Singapore :   3.29 MiB/s |   26.29 Mbps  | ping 173.479ms Linode, Tokyo, Japan :  20.45 MiB/s |  163.61 Mbps  | ping 109.322ms Linode, Singapore    :   9.33 MiB/s |   74.64 Mbps  | ping 178.288ms Vultr, Tokyo, Japan  :  19.96 MiB/s |  159.70 Mbps  | ping 117.245ms

IO test

 ## IO Test CPU Speed: bzip2 512MB -   129 MB/s sha256 512MB -   217 MB/s md5sum 512MB -   599 MB/s Disk Speed (512MB): I/O Speed  - 1.1 GB/s I/O Direct - 682 MB/s RAM Speed (493MB): Avg. write - 4744.5 MB/s Avg. read  - 9557.3 MB/s

6. Route test

 Beijing Telecom traceroute to 220.181.22.1 (220.181.22.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  0.59 ms  http: json  http: json 6  218.30.54.72  2.98 ms  http: json  http: json 7  202.97.92.46  1.10 ms  http: json  http: json 8  202.97.41.197  148.59 ms  http: json  http: json 9  202.97.12.153  152.24 ms  http: json  http: json 10  202.97.48.249  163.29 ms  http: json  http: json 11  180.149.128.50  153.57 ms  http: json  http: json 12  218.30.28.174  156.01 ms  http: json  http: json 13  220.181.16.114  272.11 ms  http: json  http: json 14  * 15  * 16  * 17  * 18  * 19  * 20  * 21  * 22  * 23  * 24  * 25  * 26  * 27  * 28  * 29  * 30  * ---------------------------------------------------------------------- Liaoning Unicom traceroute to 220.201.8.6 (220.201.8.6), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  las-b4-link.ip.twelve99.net (62.115.149.36)  1.10 ms  http: json  http: json 6  las-b2-link.ip.twelve99.net (62.115.125.163)  0.44 ms  http: json  http: json 7  las-b2-link.ip.twelve99.net (62.115.125.163)  22.18 ms  http: json  http: json 8  chinaunicom-ic155914-las-bb1.ip.twelve99-cust.net (213.248.82.206)  19.48 ms  http: json  http: json 9  219.158.96.25  152.59 ms  http: json  http: json 10  219.158.3.145  157.38 ms  http: json  http: json 11  * 12  219.158.105.90  157.15 ms  http: json  http: json 13  218.61.254.226  170.59 ms  http: json  http: json 14  218.61.254.202  174.48 ms  http: json  http: json 15  * 16  218.61.252.149  160.50 ms  http: json  http: json 17  * 18  218.61.252.149  165.98 ms  http: json  http: json 19  * 20  218.61.252.149  170.43 ms  http: json  http: json 21  * 22  218.61.252.149  154.98 ms  http: json  http: json 23  * 24  218.61.252.149  170.57 ms  http: json  http: json 25  218.61.252.150  158.09 ms  http: json  http: json 26  218.61.252.149  166.23 ms  http: json  http: json 27  * 28  218.61.252.149  159.04 ms  http: json  http: json 29  218.61.252.150  166.59 ms  http: json  http: json 30  218.61.252.149  172.11 ms  http: json  http: json ---------------------------------------------------------------------- Beijing Mobile traceroute to 221.130.33.1 (221.130.33.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  china-mobile.as58453.any2ix.coresite.com (206.72.210.219)  8.13 ms  http: json  http: json 6  223.120.6.17  8.36 ms  http: json  http: json 7  223.120.13.2  187.84 ms  http: json  http: json 8  221.183.55.102  192.25 ms  http: json  http: json 9  221.183.46.250  204.93 ms  http: json  http: json 10  221.176.21.229  191.82 ms  http: json  http: json 11  111.24.2.101  189.09 ms  http: json  http: json 12  111.24.2.134  193.28 ms  http: json  http: json 13  211.136.66.129  190.20 ms  http: json  http: json 14  221.179.159.238  190.89 ms  http: json  http: json 15  221.130.33.1  189.50 ms  http: json  http: json ---------------------------------------------------------------------- Hangzhou Telecom traceroute to 60.176.0.1 (60.176.0.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  0.30 ms  http: json  http: json 6  218.30.54.72  1.08 ms  http: json  http: json 7  202.97.83.241  2.72 ms  http: json  http: json 8  202.97.70.129  147.52 ms  http: json  http: json 9  202.97.74.2  146.02 ms  http: json  http: json 10  202.97.24.189  143.74 ms  http: json  http: json 11  202.97.101.194  158.48 ms  http: json  http: json 12  * 13  60.176.0.1  140.86 ms  http: json  http: json ---------------------------------------------------------------------- Ningbo Unicom traceroute to 60.12.17.1 (60.12.17.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  las-b4-link.ip.twelve99.net (62.115.149.36)  0.39 ms  http: json  http: json 6  las-b2-link.ip.twelve99.net (62.115.125.163)  2.07 ms  http: json  http: json 7  las-b2-link.ip.twelve99.net (62.115.125.163)  0.82 ms  http: json  http: json 8  chinaunicom-ic324374-las-b24.ip.twelve99-cust.net (62.115.154.91)  7.59 ms  http: json  http: json 9  219.158.16.93  166.79 ms  http: json  http: json 10  219.158.3.137  167.41 ms  http: json  http: json 11  * 12  219.158.107.154  192.31 ms  http: json  http: json 13  * 14  221.12.33.37  175.71 ms  http: json  http: json 15  * 16  60.12.17.1  184.30 ms  http: json  http: json ---------------------------------------------------------------------- Hangzhou Mobile traceroute to 211.140.0.2 (211.140.0.2), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  china-mobile.as58453.any2ix.coresite.com (206.72.210.219)  8.14 ms  http: json  http: json 6  223.120.6.17  8.35 ms  http: json  http: json 7  223.120.13.46  180.93 ms  http: json  http: json 8  221.183.55.26  167.98 ms  http: json  http: json 9  221.176.22.205  214.17 ms  http: json  http: json 10  221.183.23.37  163.77 ms  http: json  http: json 11  221.176.22.122  205.07 ms  http: json  http: json 12  * 13  * 14  * 15  * 16  * 17  * 18  * 19  * 20  * 21  * 22  * 23  * 24  * 25  * 26  * 27  * 28  * 29  * 30  * ---------------------------------------------------------------------- Guiyang Telecom traceroute to 58.42.224.1 (58.42.224.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  * 6  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  0.77 ms  http: json  http: json 7  218.30.54.72  2.32 ms  http: json  http: json 8  202.97.50.21  0.61 ms  http: json  http: json 9  202.97.51.97  154.87 ms  http: json  http: json 10  202.97.91.146  149.32 ms  http: json  http: json 11  202.97.89.157  171.72 ms  http: json  http: json 12  * 13  61.189.177.150  172.51 ms  http: json  http: json 14  58.42.224.1  173.01 ms  http: json  http: json ---------------------------------------------------------------------- Guiyang Unicom traceroute to 58.16.28.1 (58.16.28.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  0.87 ms  http: json  http: json 6  ae2.cr5-sjc1.ip4.gtt.net (89.149.180.26)  7.86 ms  http: json  http: json 7  as4837.cr5-sjc1.ip4.gtt.net (173.205.56.178)  149.52 ms  http: json  http: json 8  219.158.97.177  170.33 ms  http: json  http: json 9  219.158.113.126  164.26 ms  http: json  http: json 10  219.158.113.109  165.76 ms  http: json  http: json 11  219.158.106.26  190.98 ms  http: json  http: json 12  * 13  58.16.28.1  190.84 ms  http: json  http: json ---------------------------------------------------------------------- Guiyang Mobile traceroute to 211.139.0.10 (211.139.0.10), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  china-mobile.as58453.any2ix.coresite.com (206.72.210.219)  8.15 ms  http: json  http: json 6  223.120.6.17  8.32 ms  http: json  http: json 7  223.120.12.10  177.08 ms  http: json  http: json 8  221.183.55.78  163.63 ms  http: json  http: json 9  221.176.20.5  162.94 ms  http: json  http: json 10  221.183.68.138  172.68 ms  http: json  http: json 11  111.24.5.193  164.97 ms  http: json  http: json 12  111.24.5.94  186.57 ms  http: json  http: json 13  111.24.12.58  176.47 ms  http: json  http: json 14  211.139.13.142  187.71 ms  http: json  http: json 15  211.139.0.10  197.37 ms  http: json  http: json ---------------------------------------------------------------------- Guangzhou Telecom traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  * 6  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  7.11 ms  http: json  http: json 7  218.30.54.72  2.46 ms  http: json  http: json 8  202.97.93.165  1.28 ms  http: json  http: json 9  202.97.83.221  155.59 ms  http: json  http: json 10  202.97.91.146  156.00 ms  http: json  http: json 11  202.97.90.161  165.90 ms  http: json  http: json 12  113.96.5.62  168.61 ms  http: json  http: json 13  113.96.4.226  166.69 ms  http: json  http: json 14  * 15  183.56.129.2  176.71 ms  http: json  http: json 16  14.215.116.1  165.74 ms  http: json  http: json ---------------------------------------------------------------------- Shenzhen Unicom traceroute to 58.250.0.1 (58.250.0.1), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  las-b4-link.ip.twelve99.net (62.115.149.36)  0.39 ms  http: json  http: json 6  las-b2-link.ip.twelve99.net (62.115.125.163)  2.46 ms  http: json  http: json 7  las-b2-link.ip.twelve99.net (62.115.125.163)  3.94 ms  http: json  http: json 8  chinaunicom-ic-151188-las-bb1.ip.twelve99.net (213.248.94.126)  16.87 ms  http: json  http: json 9  219.158.96.25  164.97 ms  http: json  http: json 10  219.158.16.69  143.93 ms  http: json  http: json 11  219.158.5.149  154.81 ms  http: json  http: json 12  219.158.7.22  195.90 ms  http: json  http: json 13  157.148.0.50  181.79 ms  http: json  http: json 14  58.250.0.1  179.43 ms  http: json  http: json ---------------------------------------------------------------------- Guangzhou Mobile traceroute to 211.139.145.34 (211.139.145.34), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  china-mobile.as58453.any2ix.coresite.com (206.72.210.219)  8.26 ms  http: json  http: json 6  223.120.6.17  8.43 ms  http: json  http: json 7  223.120.12.106  161.20 ms  http: json  http: json 8  221.183.55.82  154.17 ms  http: json  http: json 9  221.183.25.118  149.19 ms  http: json  http: json 10  221.183.68.138  157.76 ms  http: json  http: json 11  111.24.4.245  155.53 ms  http: json  http: json 12  * 13  211.136.208.13  157.75 ms  http: json  http: json 14  211.136.249.109  159.72 ms  http: json  http: json 15  120.198.206.158  162.25 ms  http: json  http: json 16  211.139.130.202  161.68 ms  http: json  http: json 17  221.179.44.57  168.59 ms  http: json  http: json 18  * 19  * 20  * 21  * 22  * 23  * 24  * 25  * 26  * 27  * 28  * 29  * 30  * ---------------------------------------------------------------------- Shanghai Telecom traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  12.62 ms  http: json  http: json 6  218.30.54.72  2.26 ms  http: json  http: json 7  202.97.83.241  13.66 ms  http: json  http: json 8  202.97.41.201  132.23 ms  http: json  http: json 9  * 10  202.97.57.150  140.92 ms  http: json  http: json 11  * 12  101.95.120.109  139.21 ms  http: json  http: json ---------------------------------------------------------------------- Shanghai Unicom traceroute to 211.95.72.254 (211.95.72.254), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  et-0-0-61.cr3-lax2.ip4.gtt.net (76.74.41.89)  0.50 ms  http: json  http: json 6  ae10.cr4-lax2.ip4.gtt.net (89.149.130.90)  3.07 ms  http: json  http: json 7  as4837.cr4-lax2.ip4.gtt.net (173.241.128.46)  3.33 ms  http: json  http: json 8  219.158.96.29  174.02 ms  http: json  http: json 9  219.158.96.210  170.30 ms  http: json  http: json 10  219.158.103.217  174.06 ms  http: json  http: json 11  219.158.6.233  177.33 ms  http: json  http: json 12  * 13  112.64.246.218  176.97 ms  http: json  http: json 14  * 15  * 16  * 17  * 18  * 19  * 20  * 21  * 22  * 23  * 24  * 25  * 26  * 27  * 28  * 29  * 30  * ---------------------------------------------------------------------- Shanghai Mobile traceroute to 183.192.160.3 (183.192.160.3), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  * 6  china-mobile.as58453.any2ix.coresite.com (206.72.210.219)  8.25 ms  http: json  http: json 7  223.120.6.17  8.39 ms  http: json  http: json 8  223.120.13.46  179.27 ms  http: json  http: json 9  221.183.55.30  157.44 ms  http: json  http: json 10  221.183.25.189  160.92 ms  http: json  http: json 11  221.176.22.9  186.26 ms 12  111.24.3.81  187.94 ms 13  * 14  117.185.10.242  190.47 ms 15  120.204.194.14  208.26 ms 16  120.204.197.126  187.81 ms 17  * 18  * 19  * 20  * 21  * 22  * 23  * 24  * 25  * 26  * 27  * 28  * 29  * 30  * ---------------------------------------------------------------------- Chengdu Education Network traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 60 byte packets 1  * 2  * 3  * 4  * 5  xe-0-0-22-0.a00.lsanca07.us.bb.gin.ntt.net (129.250.207.189)  0.34 ms 6  ae-7.r24.lsanca07.us.bb.gin.ntt.net (129.250.2.105)  1.31 ms 7  ae-1.r00.lsanca07.us.bb.gin.ntt.net (129.250.3.17)  0.93 ms 8  * 9  38.88.196.186  162.26 ms 10  101.4.117.169  163.19 ms 11  101.4.117.97  166.56 ms 12  101.4.114.170  167.15 ms 13  101.4.112.14  181.92 ms 14  101.4.112.18  200.87 ms 15  101.4.116.158  196.22 ms 16  * 17  * 18  * 19  202.112.14.151  188.85 ms

8. National ping

Judging from the ping value, they are all direct lines, which confirms the above route.

9、Geekbench 5 Benchmark Test

Single core: 986, single core performance is very strong!

Details: https://browser.geekbench.com/v5/cpu/8564751/claim?key=868768

10. Final

The machine has strong performance and 10G bandwidth.

Under the summary of lines, the three networks are directly connected to each other in both directions, and they all follow their own backbone lines.

It is still suitable to build a website. If you are a novice, you can live for a gift of $100 or $50, which will be fun for you for a month.