HotlineServers Benchmark (8GB, Montreal Location)

awang

4 years ago

In this review

Plan Specifications
Server Benchmarks

This is a followup post for my recent review of HotlineServers.com. Note that this post will only contain benchmarks for the 8GB plan in HotlineServers’s Montreal location. For a full review of the provider, please check out the linked post above.

Additionally, this post will also contain some additional tests for the network, like a traceroute to various locations on the internet (to determine how the routing in the location looks).

The VM being benchmarked here was generously loaned to me by @iroshan464 over at the LowEndSpirit forum. Thank you iroshan464!

Plan Specifications

4 dedicated? threads, Intel Xeon E5-2650 v2

8GB RAM (type unclear)

160GB SSD storage, RAID10

1 Gbit network

10TB bandwidth

1 IPv4 Address, 5 IPv6 Addresses on request (from a /64). Additional IPv4 are $2/mo each.

KVM virtualization

Cologix (GTHost) datacenter in Montreal, QC, CA

Free DirectAdmin license

Free nightly offsite backups

$6.53 USD per month

Server Benchmarks

YABS.sh

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2020-06-20                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Sat 04 Jul 2020 11:42:55 AM EDT

Basic System Information:
---------------------------------
Processor  : Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
CPU cores  : 4 @ 2599.998 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       | 225.76 MB/s  (56.4k) | 1.99 GB/s    (31.1k)
Write      | 226.35 MB/s  (56.5k) | 2.00 GB/s    (31.3k)
Total      | 452.11 MB/s (113.0k) | 4.00 GB/s    (62.5k)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 1.34 GB/s     (2.6k) | 1.07 GB/s     (1.0k)
Write      | 1.41 GB/s     (2.7k) | 1.14 GB/s     (1.1k)
Total      | 2.76 GB/s     (5.3k) | 2.21 GB/s     (2.1k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider                  | Location (Link)           | Send Speed      | Recv Speed
                          |                           |                 |
Bouygues Telecom          | Paris, FR (10G)           | 871 Mbits/sec   | 242 Mbits/sec
Online.net                | Paris, FR (10G)           | 893 Mbits/sec   | 237 Mbits/sec
WorldStream               | The Netherlands (10G)     | 876 Mbits/sec   | 218 Mbits/sec
wilhelm.tel               | Hamburg, DE (10G)         | 871 Mbits/sec   | 307 Mbits/sec
Biznet                    | Bogor, Indonesia (1G)     | 532 Mbits/sec   | 56.4 Mbits/sec
Hostkey                   | Moscow, RU (1G)           | 858 Mbits/sec   | 749 Mbits/sec
Velocity Online           | Tallahassee, FL, US (10G) | 913 Mbits/sec   | 596 Mbits/sec
Airstream Communications  | Eau Claire, WI, US (10G)  | 912 Mbits/sec   | 834 Mbits/sec
Hurricane Electric        | Fremont, CA, US (10G)     | 908 Mbits/sec   | 469 Mbits/sec

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 554
Multi Core      | 2090
Full Test       | https://browser.geekbench.com/v5/cpu/2805149

Nench.sh

-------------------------------------------------
 nench.sh v2019.07.20 -- https://git.io/nench.sh
 benchmark timestamp:    2020-07-04 15:56:02 UTC
-------------------------------------------------

Processor:    Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz
CPU cores:    4
Frequency:    2599.998 MHz
RAM:          7.7Gi
Swap:         1.0Gi
Kernel:       Linux 4.19.0-9-amd64 x86_64

Disks:
vda    160G  HDD

CPU: SHA256-hashing 500 MB
    3.298 seconds
CPU: bzip2-compressing 500 MB
    5.856 seconds
CPU: AES-encrypting 500 MB
    2.342 seconds

ioping: seek rate
    min/avg/max/mdev = 41.6 us / 76.5 us / 4.77 ms / 50.1 us
ioping: sequential read speed
    generated 28.0 k requests in 5.00 s, 6.83 GiB, 5.60 k iops, 1.37 GiB/s

dd: sequential write speed
    1st run:    190.73 MiB/s
    2nd run:    201.23 MiB/s
    3rd run:    214.58 MiB/s
    average:    202.18 MiB/s

IPv4 speedtests
    your IPv4:    158.51.120.xxxx

    Cachefly CDN:         90.83 MiB/s
    Leaseweb (NL):        16.67 MiB/s
    Softlayer DAL (US):   26.69 MiB/s
    Online.net (FR):      14.45 MiB/s
    OVH BHS (CA):         66.76 MiB/s

No IPv6 connectivity detected
-------------------------------------------------

Speedtest.net

Traceroute to Cloudflare.com

traceroute to cloudflare.com (104.17.175.85), 30 hops max, 60 byte packets
 1  158.51.120.129 (158.51.120.129)  0.342 ms  0.300 ms  0.274 ms
 2  ae1-1414.cr0-mtl3.ip4.gtt.net (209.120.145.113)  2.057 ms  2.034 ms  2.000 ms
 3  ae0.cr2-nyc4.ip4.gtt.net (213.200.112.166)  8.635 ms  8.612 ms  24.863 ms
 4  ip4.gtt.net (208.116.240.226)  30.801 ms  18.428 ms  30.746 ms
 5  104.17.175.85 (104.17.175.85)  13.626 ms  13.592 ms  13.555 ms

Traceroute to Google.com

traceroute to google.com (172.217.168.206), 30 hops max, 60 byte packets
 1  158.51.120.129 (158.51.120.129)  0.340 ms  0.307 ms  0.283 ms
 2  ae1-1414.cr0-mtl3.ip4.gtt.net (209.120.145.113)  0.485 ms  0.446 ms  0.413 ms
 3  ae.cr0-tor1.ip4.gtt.net (89.149.187.241)  7.427 ms  7.340 ms  7.325 ms
 4  74.125.147.196 (74.125.147.196)  7.462 ms  7.454 ms  10.640 ms
 5  108.170.250.227 (108.170.250.227)  9.353 ms 108.170.250.247 (108.170.250.247)  8.167 ms 74.125.244.163 (74.125.244.163)  7.948 ms
 6  172.253.78.118 (172.253.78.118)  15.745 ms 74.125.37.44 (74.125.37.44)  15.903 ms  15.867 ms
 7  172.253.65.175 (172.253.65.175)  89.207 ms 172.253.65.167 (172.253.65.167)  83.203 ms 172.253.65.175 (172.253.65.175)  89.173 ms
 8  209.85.245.230 (209.85.245.230)  88.567 ms  88.747 ms  88.319 ms
 9  209.85.255.231 (209.85.255.231)  88.690 ms 216.239.42.102 (216.239.42.102)  87.924 ms 216.239.42.171 (216.239.42.171)  88.945 ms
10  108.170.241.225 (108.170.241.225)  89.095 ms  89.098 ms  88.968 ms
11  108.170.227.3 (108.170.227.3)  88.650 ms 108.170.227.9 (108.170.227.9)  88.710 ms 108.170.227.3 (108.170.227.3)  89.162 ms
12  ams16s32-in-f14.1e100.net (172.217.168.206)  88.085 ms  88.071 ms  88.514 ms

Traceroute to Akamai.com

traceroute to akamai.com (23.67.80.42), 30 hops max, 60 byte packets
 1  158.51.120.129 (158.51.120.129)  0.328 ms  0.278 ms  0.265 ms
 2  ae1-1414.cr0-mtl3.ip4.gtt.net (209.120.145.113)  0.482 ms  0.460 ms  0.429 ms
 3  ae24.cr4-nyc6.ip4.gtt.net (213.200.121.6)  9.039 ms  9.044 ms  9.003 ms
 4  ip4.gtt.net (98.124.184.66)  8.794 ms  8.739 ms  8.706 ms
 5  ae2.r02.lga01.icn.netarch.akamai.com (23.203.156.40)  13.520 ms  13.501 ms  13.468 ms
 6  ae5.r01.iad01.icn.netarch.akamai.com (23.32.63.7)  14.185 ms  13.785 ms  13.751 ms
 7  ae1.r01.iad01.ien.netarch.akamai.com (23.203.152.35)  27.452 ms  27.414 ms  27.404 ms
 8  ae2.ctl-iad3.netarch.akamai.com (23.203.152.215)  43.125 ms  18.734 ms  18.701 ms
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
// truncated

Traceroute to Level3.net

traceroute to level3.net (4.68.80.110), 30 hops max, 60 byte packets
 1  158.51.120.129 (158.51.120.129)  0.536 ms  0.492 ms  0.462 ms
 2  ae1-1414.cr0-mtl3.ip4.gtt.net (209.120.145.113)  0.516 ms  0.472 ms  0.401 ms
 3  ae.cr0-tor1.ip4.gtt.net (89.149.187.241)  9.767 ms  11.019 ms  9.680 ms
 4  4.68.39.41 (4.68.39.41)  8.913 ms  8.887 ms  8.795 ms
 5  * * *
 6  4.68.94.50 (4.68.94.50)  87.714 ms  46.473 ms  46.392 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
//truncated

For the most part, the results of the benchmarks are similar to that of my Chicago VPS. However, the download speeds to some locations are interestingly low. Maybe this will be fixed in the future. I/O is also somewhat higher for larger block sizes.

Unfortunately, IPv6 was not configured on this machine so I was not able to benchmark it.