This is another followup post for my recent review of HotlineServers.com. Note that this post will only contain benchmarks for the 8GB plan in HotlineServers’s Miami location. For a full review of the provider, please check out the linked post above.
Like the Montreal benchmark, this post will also contain some additional tests for the network.
The VM being benchmarked here was generously loaned to me by @Ouji over at the LowEndSpirit forum. Thank you Ouji!
Plan Specifications
Server Benchmarks
YABS.sh
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
# Yet-Another-Bench-Script #
# v2020-06-20 #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
Sat 04 Jul 2020 05:25:07 PM EDT
Basic System Information:
---------------------------------
Processor : AMD Ryzen 9 3900X 12-Core Processor
CPU cores : 4 @ 3792.874 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 7.7Gi
Swap : 1.0Gi
Disk : 157G
fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 286.00 MB/s (71.5k) | 2.32 GB/s (36.2k)
Write | 286.75 MB/s (71.6k) | 2.33 GB/s (36.4k)
Total | 572.75 MB/s (143.1k) | 4.65 GB/s (72.7k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.12 GB/s (2.1k) | 1.04 GB/s (1.0k)
Write | 1.18 GB/s (2.3k) | 1.10 GB/s (1.0k)
Total | 2.30 GB/s (4.5k) | 2.14 GB/s (2.0k)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed
| | |
Bouygues Telecom | Paris, FR (10G) | 344 Mbits/sec | 507 Mbits/sec
Online.net | Paris, FR (10G) | 314 Mbits/sec | 672 Mbits/sec
WorldStream | The Netherlands (10G) | 327 Mbits/sec | 857 Mbits/sec
wilhelm.tel | Hamburg, DE (10G) | 261 Mbits/sec | 368 Mbits/sec
Biznet | Bogor, Indonesia (1G) | 165 Mbits/sec | 266 Mbits/sec
Hostkey | Moscow, RU (1G) | 349 Mbits/sec | 820 Mbits/sec
Velocity Online | Tallahassee, FL, US (10G) | 919 Mbits/sec | 938 Mbits/sec
Airstream Communications | Eau Claire, WI, US (10G) | 588 Mbits/sec | 912 Mbits/sec
Hurricane Electric | Fremont, CA, US (10G) | 311 Mbits/sec | 298 Mbits/sec
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 1232
Multi Core | 3830
Full Test | https://browser.geekbench.com/v5/cpu/2808428Nench.sh
-------------------------------------------------
nench.sh v2019.07.20 -- https://git.io/nench.sh
benchmark timestamp: 2020-07-04 21:32:15 UTC
-------------------------------------------------
Processor: AMD Ryzen 9 3900X 12-Core Processor
CPU cores: 4
Frequency: 3792.874 MHz
RAM: 7.7Gi
Swap: 1.0Gi
Kernel: Linux 4.19.0-5-amd64 x86_64
Disks:
vda 160G HDD
CPU: SHA256-hashing 500 MB
1.948 seconds
CPU: bzip2-compressing 500 MB
4.096 seconds
CPU: AES-encrypting 500 MB
0.980 seconds
ioping: seek rate
min/avg/max/mdev = 21.6 us / 45.2 us / 1.23 ms / 11.1 us
ioping: sequential read speed
generated 48.2 k requests in 5.00 s, 11.8 GiB, 9.65 k iops, 2.36 GiB/s
dd: sequential write speed
1st run: 491.14 MiB/s
2nd run: 488.28 MiB/s
3rd run: 468.25 MiB/s
average: 482.56 MiB/s
IPv4 speedtests
your IPv4: 139.64.236.xxxx
Cachefly CDN: 55.34 MiB/s
Leaseweb (NL): 20.75 MiB/s
Softlayer DAL (US): 60.18 MiB/s
Online.net (FR): 21.08 MiB/s
OVH BHS (CA): 50.68 MiB/s
No IPv6 connectivity detected
-------------------------------------------------Speedtest.net
Traceroute to Cloudflare.com
traceroute to cloudflare.com (104.17.176.85), 30 hops max, 60 byte packets
1 139.64.236.1 (139.64.236.1) 0.345 ms 0.326 ms 1.497 ms
2 206.41.108.18 (206.41.108.18) 1.596 ms 1.820 ms 1.804 ms
3 104.17.176.85 (104.17.176.85) 0.351 ms 0.433 ms 0.429 msTraceroute to Google.com
traceroute to google.com (74.125.134.139), 30 hops max, 60 byte packets
1 139.64.236.1 (139.64.236.1) 0.233 ms 0.186 ms 0.199 ms
2 ae0-200.cr8-mia1.ip4.gtt.net (209.120.147.1) 0.948 ms 1.279 ms 0.910 ms
3 ae4.cr2-atl1.ip4.gtt.net (89.149.185.230) 15.883 ms 15.866 ms 15.873 ms
4 as15169.atl12.ip4.gtt.net (199.229.231.230) 15.258 ms 15.235 ms 15.215 ms
5 * * *
6 108.170.225.126 (108.170.225.126) 15.147 ms 108.170.249.97 (108.170.249.97) 15.826 ms 108.170.249.33 (108.170.249.33) 15.986 ms
7 108.170.249.163 (108.170.249.163) 15.797 ms 108.170.249.67 (108.170.249.67) 15.978 ms 16.095 ms
8 209.85.250.96 (209.85.250.96) 16.181 ms 72.14.233.145 (72.14.233.145) 16.317 ms 108.170.236.128 (108.170.236.128) 15.899 ms
9 66.249.95.219 (66.249.95.219) 21.889 ms 216.239.56.52 (216.239.56.52) 20.685 ms 66.249.95.219 (66.249.95.219) 21.869 ms
10 216.239.42.63 (216.239.42.63) 19.950 ms 74.125.252.140 (74.125.252.140) 19.795 ms 216.239.42.63 (216.239.42.63) 40.548 ms
11 216.239.59.95 (216.239.59.95) 21.946 ms 216.239.56.123 (216.239.56.123) 22.837 ms 216.239.56.121 (216.239.56.121) 21.148 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 vj-in-f139.1e100.net (74.125.134.139) 19.671 ms 20.172 ms *Traceroute to Akamai.com
traceroute to akamai.com (23.67.80.42), 30 hops max, 60 byte packets
1 139.64.236.1 (139.64.236.1) 0.220 ms 0.420 ms 0.405 ms
2 ae0-200.cr8-mia1.ip4.gtt.net (209.120.147.1) 1.037 ms 1.008 ms 1.004 ms
3 ae3.cr2-atl2.ip4.gtt.net (141.136.111.22) 16.248 ms 16.237 ms 21.444 ms
4 ip4.gtt.net (98.124.189.26) 16.239 ms 16.223 ms 16.191 ms
5 ae2.r01.atl01.icn.netarch.akamai.com (23.203.144.36) 27.474 ms 27.460 ms 27.443 ms
6 ae13.r02.iad01.icn.netarch.akamai.com (23.32.63.100) 29.290 ms 29.544 ms 29.341 ms
7 ae2.r01.iad01.ien.netarch.akamai.com (23.203.152.39) 29.785 ms 29.762 ms 29.725 ms
8 ae2.ctl-iad3.netarch.akamai.com (23.203.152.215) 114.820 ms 114.812 ms 114.795 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
//truncatedTraceroute to Level3.net
traceroute to level3.net (4.68.80.110), 30 hops max, 60 byte packets
1 139.64.236.1 (139.64.236.1) 0.425 ms 0.394 ms 5.503 ms
2 ae0-200.cr8-mia1.ip4.gtt.net (209.120.147.1) 0.657 ms 1.148 ms 0.613 ms
3 * * *
4 * * *
5 4.68.94.50 (4.68.94.50) 48.562 ms 48.544 ms 48.523 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
//truncatedCPU and I/O performance both far exceed the Chicago and Montreal locations – I guess this is the benefit of a Ryzen CPU and NVMe drives. However, networking performance is unfortunately quite poor (relatively speaking) to locations in Europe and the West Coast.
Unfortunately, IPv6 was not configured on this machine so I was not able to benchmark IPv6.