Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Black Friday 2021 - NVMe and Storage deals - Deploy in 16 global locations (APAC/EU/US) - Page 52
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Black Friday 2021 - NVMe and Storage deals - Deploy in 16 global locations (APAC/EU/US)

1…4950525455

Comments

  • aj_potcaj_potc Member

    @EasyCompany251 said:
    Does HostHatch run its own internal network between locations? Seems strange that they would have such problematic slow network speeds within their own network.

    No, they don't have their own network spanning datacenters. They claim to choose datacenters with very premium networks, so each one is independent in that regard.

    I'm unclear whether they negotiate their peering and transit separately, or if they just take each datacenter's own BGP blend. I guess it might differ from one datacenter to the other. But this would certainly affect how proactive they can be (i.e., it's one thing if they are a direct client of Telia or GTT, but it might be another if they need to run everything through their colocation partner).

    Wow that sucks. I can say the same in the last couple of weeks with my own support ticket. I got them to switch the routes around and to move me to another node in Chicago - no difference. Sigh.....

    Honestly I can't condemn them so harshly. It's really the same with every provider I've used. The more premium (expensive) ones may be a little more active in contacting their upstreams, but unless the issue is within their own network (which almost never happens in my experience), it's a matter of luck whether anything gets solved. Sometimes it's a transient routing issue and goes away quickly; other times it's a capacity issue that can't be solved without some effort; and yet other times, nobody can seem to reproduce the issue or even cares about it. The last case is of course the worst when it affects you.

    What also surprises me is that not more people have complained... I assume people are using these storage servers for storage so when you move data in and out of HostHatch you are bound to see these slow transfers...

    I wonder this about most of these problems -- again, not with HostHatch in particular. If I can reproduce slow transfers on certain paths, certainly the guys sitting in the NOCs can see it, too, right? In that case they can at least inform their customers that there's a problem, and not force everybody to do endless MTRs to prove it, and then act like it's a big surprise when they see that some link is at its capacity. :smile:

  • skorousskorous Member

    @EasyCompany251 said:

    What also surprises me is that not more people have complained... I assume people are using these storage servers for storage so when you move data in and out of HostHatch you are bound to see these slow transfers...

    Depends on where you're moving it to I guess. Plus I generally throttle my transfers anyway.

  • EasyCompany251EasyCompany251 Member
    edited January 2022

    @skorous said:
    Depends on where you're moving it to I guess. Plus I generally throttle my transfers anyway.

    I mean it's possible it's path specific but it seems more widespread than that. They changed a bunch of routes ranging from GTT to NTT but had no effect. At the end of the day, it's literally going from Chicago to New York. It's not like it's going from Chicago to across the globe to Singapore/Tokyo or other Asia Pacific regions.

    Then you also have @aj_potc - who was transferring between HostHatch servers in NY and Chicago and still saw slowdowns.

  • EasyCompany251EasyCompany251 Member

    HostHatch finally got back to me that they are investigating with Psychz for their Chicago location.

  • PieHasBeenEatenPieHasBeenEaten Member, Host Rep

    Awesome! I got a couple servers with them in Chicago and it is slow. I just quit using them period. There NL location works great!

    Thanked by 1FrankZ
  • fluffernutterfluffernutter Member

    Yeah my Chicago servers have ended up just being idlers. Every other location is fantastic, big fan of their NL one as well, super good network there.

  • DecicusDecicus Member

    Anyone gotten their Oslo server(s) deployed yet? Mine is still pending at least.

  • defaultdefault Veteran
    edited February 2022

    Confirmed. Chicago bandwidth is absolute rubbish for quite some time now.

    They might as well shutdown servers, to idle in cold state, in order to protect the planet by not consuming electricity for nothing.

    Edit: tagging @hosthatch and @Emil without hope.

    Thanked by 2webcraft FrankZ
  • EasyCompany251EasyCompany251 Member

    wow.....seems like quite a few people having issues with Chicago.......who would've known.....

  • DecicusDecicus Member

    @Decicus said:
    Anyone gotten their Oslo server(s) deployed yet? Mine is still pending at least.

    My question aged well it seems. My Oslo server was just deployed :joy:

  • notsocoolnotsocool Member

    Also got my Oslo server provisioned today.

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Yet-Another-Bench-Script

    v2021-12-28

    https://github.com/masonr/yet-another-bench-script

    ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##

    Thu Feb 3 20:04:55 UTC 2022

    Basic System Information:

    Processor : AMD EPYC 7413 24-Core Processor
    CPU cores : 4 @ 2645.030 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM : 19.6 GiB
    Swap : 0.0 KiB
    Disk : 90.2 GiB

    fio Disk Speed Tests (Mixed R/W 50/50):

    Block Size 4k (IOPS) 64k (IOPS)
    Read 277.62 MB/s (69.4k) 3.15 GB/s (49.2k)
    Write 278.35 MB/s (69.5k) 3.16 GB/s (49.4k)
    Total 555.97 MB/s (138.9k) 6.31 GB/s (98.6k)
    Block Size 512k (IOPS) 1m (IOPS)
    ------ --- ---- ---- ----
    Read 5.53 GB/s (10.8k) 5.78 GB/s (5.6k)
    Write 5.83 GB/s (11.3k) 6.16 GB/s (6.0k)
    Total 11.36 GB/s (22.2k) 11.94 GB/s (11.6k)

    iperf3 Network Speed Tests (IPv4):

    Provider | Location (Link) | Send Speed | Recv Speed
    | | |
    Clouvider | London, UK (10G) | 1.19 Gbits/sec | 66.9 Mbits/sec
    Online.net | Paris, FR (10G) | 2.64 Gbits/sec | 2.72 Gbits/sec
    WorldStream | The Netherlands (10G) | 3.69 Gbits/sec | 3.93 Gbits/sec
    WebHorizon | Singapore (400M) | 247 Mbits/sec | 426 Mbits/sec
    Clouvider | NYC, NY, US (10G) | 910 Mbits/sec | 974 Mbits/sec
    Velocity Online | Tallahassee, FL, US (10G) | 802 Mbits/sec | 1.53 Gbits/sec
    Clouvider | Los Angeles, CA, US (10G) | 734 Mbits/sec | 838 Mbits/sec
    Iveloz Telecom | Sao Paulo, BR (2G) | 119 Mbits/sec | 791 Mbits/sec

    Geekbench 5 Benchmark Test:

    Test | Value
    |
    Single Core | 1141
    Multi Core | 4114
    Full Test | https://browser.geekbench.com/v5/cpu/12569715

    Thanked by 1nobizzle
  • kheng86kheng86 Member

    yes.. I do have network issue with the Chicago VPS

  • defaultdefault Veteran
    edited February 2022

    @hosthatch @Emil - all my Chicago servers are down. Any info?

    EDIT: Did you decide to finally shutdown that location, until you get better connection there?

    Thanked by 1darkimmortal
  • webcraftwebcraft Member

    Has IPv6 been deployed at all locations in the new panel?

  • FrankZFrankZ Veteran

    Chicago seems to be back up now.

  • yoursunnyyoursunny Member, IPv6 Advocate

    @default said:
    @hosthatch @Emil - all my Chicago servers are down. Any info?
    Did you decide to finally shutdown that location, until you get better connection there?

    Chicago network had a 33-minute downtime since 08:00 Chicago time.
    The sheer amount of push-ups rsync'ed through this network has crashed the router.
    We apologize for the lost billions.

    Thanked by 1FrankZ
  • EasyCompany251EasyCompany251 Member
    edited February 2022

    Well at least HostHatch is doing some work on their Chicago servers.

    Ran another quick iperf and it seems like Chicago -> New York (BuyVM) is getting roughly 300 Mbps - decent improvement compared to the last test in which speeds dropped to 40 Mbps.

    On the other hand, BUYVM (NY) -> Chicago (HostHatch) is in excess of 600 Mbps.

    So maybe HostHatch's solution isn't fully implemented yet....

    Their twitter says that they are looking at a Chicago network issue.

  • EasyCompany251EasyCompany251 Member
    edited February 2022

    HostHatch Chicago -> BuyVM NY

    root@localhost:~# iperf3 -c  HOSTHATCH -R -t 60
Connecting to host HOSTHATCH , port 5201
Reverse mode, remote host HOSTHATCH  is sending
[  5] local BUYVM port 53992 connected to HOSTHATCH  port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  50.9 MBytes   427 Mbits/sec
[  5]   1.00-2.00   sec  37.1 MBytes   311 Mbits/sec
[  5]   2.00-3.00   sec  39.5 MBytes   331 Mbits/sec
[  5]   3.00-4.00   sec  39.0 MBytes   327 Mbits/sec
[  5]   4.00-5.00   sec  42.3 MBytes   355 Mbits/sec
[  5]   5.00-6.00   sec  42.6 MBytes   358 Mbits/sec
[  5]   6.00-7.00   sec  44.4 MBytes   372 Mbits/sec
[  5]   7.00-8.00   sec  45.4 MBytes   380 Mbits/sec
[  5]   8.00-9.00   sec  40.2 MBytes   338 Mbits/sec
[  5]   9.00-10.00  sec  36.9 MBytes   309 Mbits/sec
[  5]  10.00-11.00  sec  40.2 MBytes   337 Mbits/sec
[  5]  11.00-12.00  sec  39.8 MBytes   334 Mbits/sec
[  5]  12.00-13.00  sec  32.7 MBytes   274 Mbits/sec
[  5]  13.00-14.00  sec  34.0 MBytes   284 Mbits/sec
[  5]  14.00-15.00  sec  35.9 MBytes   302 Mbits/sec
[  5]  15.00-16.00  sec  37.6 MBytes   315 Mbits/sec
[  5]  16.00-17.00  sec  37.3 MBytes   313 Mbits/sec
[  5]  17.00-18.00  sec  40.1 MBytes   336 Mbits/sec
[  5]  18.00-19.00  sec  41.0 MBytes   344 Mbits/sec
[  5]  19.00-20.00  sec  32.1 MBytes   269 Mbits/sec
[  5]  20.00-21.00  sec  35.4 MBytes   297 Mbits/sec
[  5]  21.00-22.00  sec  39.0 MBytes   327 Mbits/sec
[  5]  22.00-23.00  sec  31.5 MBytes   264 Mbits/sec
[  5]  23.00-24.00  sec  31.2 MBytes   262 Mbits/sec
[  5]  24.00-25.00  sec  32.9 MBytes   277 Mbits/sec
[  5]  25.00-26.00  sec  34.3 MBytes   288 Mbits/sec
[  5]  26.00-27.00  sec  35.7 MBytes   299 Mbits/sec
[  5]  27.00-28.00  sec  37.2 MBytes   312 Mbits/sec
[  5]  28.00-29.00  sec  30.4 MBytes   255 Mbits/sec
[  5]  29.00-30.00  sec  31.7 MBytes   266 Mbits/sec
[  5]  30.00-31.00  sec  34.9 MBytes   293 Mbits/sec
[  5]  31.00-32.00  sec  36.5 MBytes   306 Mbits/sec
[  5]  32.00-33.00  sec  31.1 MBytes   261 Mbits/sec
[  5]  33.00-34.00  sec  28.9 MBytes   243 Mbits/sec
[  5]  34.00-35.00  sec  21.6 MBytes   181 Mbits/sec
[  5]  35.00-36.00  sec  23.8 MBytes   200 Mbits/sec
[  5]  36.00-37.00  sec  25.4 MBytes   213 Mbits/sec
[  5]  37.00-38.00  sec  27.1 MBytes   227 Mbits/sec
[  5]  38.00-39.00  sec  28.3 MBytes   237 Mbits/sec
[  5]  39.00-40.00  sec  30.4 MBytes   255 Mbits/sec
[  5]  40.00-41.00  sec  31.3 MBytes   263 Mbits/sec
[  5]  41.00-42.00  sec  25.9 MBytes   218 Mbits/sec
[  5]  42.00-43.00  sec  27.8 MBytes   233 Mbits/sec
[  5]  43.00-44.00  sec  30.7 MBytes   257 Mbits/sec
[  5]  44.00-45.00  sec  31.6 MBytes   265 Mbits/sec
[  5]  45.00-46.00  sec  32.8 MBytes   275 Mbits/sec
[  5]  46.00-47.00  sec  32.5 MBytes   272 Mbits/sec
[  5]  47.00-48.00  sec  29.7 MBytes   249 Mbits/sec
[  5]  48.00-49.00  sec  27.8 MBytes   233 Mbits/sec
[  5]  49.00-50.00  sec  24.0 MBytes   201 Mbits/sec
[  5]  50.00-51.00  sec  23.3 MBytes   195 Mbits/sec
[  5]  51.00-52.00  sec  24.7 MBytes   207 Mbits/sec
[  5]  52.00-53.00  sec  26.4 MBytes   221 Mbits/sec
[  5]  53.00-54.00  sec  27.8 MBytes   234 Mbits/sec
[  5]  54.00-55.00  sec  30.1 MBytes   252 Mbits/sec
[  5]  55.00-56.00  sec  31.9 MBytes   268 Mbits/sec
[  5]  56.00-57.00  sec  33.1 MBytes   278 Mbits/sec
[  5]  57.00-58.00  sec  33.5 MBytes   281 Mbits/sec
[  5]  58.00-59.00  sec  28.9 MBytes   242 Mbits/sec
[  5]  59.00-60.00  sec  28.3 MBytes   237 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec  1.95 GBytes   280 Mbits/sec  1485             sender
[  5]   0.00-60.00  sec  1.95 GBytes   279 Mbits/sec                  receiver

    BuyVM NY -> HostHatch Chicago

    root@localhost:~# iperf3 -c  BUYVM  -t 60
Connecting to host HOSTHATCH, port 5201
[  5] local BUYVM   port 53996 connected to HOSTHATCH port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  37.7 MBytes   316 Mbits/sec   28   1.43 MBytes
[  5]   1.00-2.00   sec  67.5 MBytes   566 Mbits/sec    0   1.47 MBytes
[  5]   2.00-3.00   sec  72.5 MBytes   608 Mbits/sec    0   1.50 MBytes
[  5]   3.00-4.00   sec  73.8 MBytes   619 Mbits/sec    0   1.53 MBytes
[  5]   4.00-5.00   sec  71.2 MBytes   598 Mbits/sec    0   1.57 MBytes
[  5]   5.00-6.00   sec  68.8 MBytes   577 Mbits/sec    0   1.60 MBytes
[  5]   6.00-7.00   sec  73.8 MBytes   618 Mbits/sec    0   1.63 MBytes
[  5]   7.00-8.00   sec  75.0 MBytes   630 Mbits/sec    0   1.66 MBytes
[  5]   8.00-9.00   sec  78.8 MBytes   661 Mbits/sec    0   1.71 MBytes
[  5]   9.00-10.00  sec  85.0 MBytes   713 Mbits/sec    0   1.79 MBytes
[  5]  10.00-11.00  sec  82.5 MBytes   692 Mbits/sec    0   1.79 MBytes
[  5]  11.00-12.00  sec  86.2 MBytes   724 Mbits/sec    0   1.79 MBytes
[  5]  12.00-13.00  sec  87.5 MBytes   734 Mbits/sec    0   1.79 MBytes
[  5]  13.00-14.00  sec  86.2 MBytes   723 Mbits/sec    0   1.79 MBytes
[  5]  14.00-15.00  sec  87.5 MBytes   734 Mbits/sec    0   1.79 MBytes
[  5]  15.00-16.00  sec  85.0 MBytes   713 Mbits/sec    0   1.79 MBytes
[  5]  16.00-17.00  sec  86.2 MBytes   723 Mbits/sec    0   1.79 MBytes
[  5]  17.00-18.00  sec  85.0 MBytes   713 Mbits/sec    0   1.79 MBytes
[  5]  18.00-19.00  sec  86.2 MBytes   724 Mbits/sec    0   1.79 MBytes
[  5]  19.00-20.00  sec  86.2 MBytes   723 Mbits/sec    0   1.79 MBytes
[  5]  20.00-21.00  sec  88.8 MBytes   745 Mbits/sec    0   1.79 MBytes
[  5]  21.00-22.00  sec  86.2 MBytes   724 Mbits/sec    0   1.79 MBytes
[  5]  22.00-23.00  sec  86.2 MBytes   724 Mbits/sec    0   1.79 MBytes
[  5]  23.00-24.00  sec  88.8 MBytes   744 Mbits/sec    0   1.79 MBytes
[  5]  24.00-25.00  sec  88.8 MBytes   744 Mbits/sec    0   1.79 MBytes
[  5]  25.00-26.00  sec  62.5 MBytes   525 Mbits/sec   37   1.38 MBytes
[  5]  26.00-27.00  sec  71.2 MBytes   598 Mbits/sec    0   1.50 MBytes
[  5]  27.00-28.00  sec  73.8 MBytes   619 Mbits/sec    0   1.59 MBytes
[  5]  28.00-29.00  sec  78.8 MBytes   661 Mbits/sec    0   1.66 MBytes
[  5]  29.00-30.00  sec  82.5 MBytes   692 Mbits/sec    0   1.71 MBytes
[  5]  30.00-31.00  sec  85.0 MBytes   713 Mbits/sec    0   1.75 MBytes
[  5]  31.00-32.00  sec  83.8 MBytes   703 Mbits/sec    0   1.77 MBytes
[  5]  32.00-33.00  sec  87.5 MBytes   734 Mbits/sec    0   1.78 MBytes
[  5]  33.00-34.00  sec  88.8 MBytes   744 Mbits/sec    0   1.78 MBytes
[  5]  34.00-35.00  sec  87.5 MBytes   734 Mbits/sec    0   1.78 MBytes
[  5]  35.00-36.00  sec  86.2 MBytes   723 Mbits/sec    0   1.78 MBytes
[  5]  36.00-37.00  sec  85.0 MBytes   713 Mbits/sec    0   1.78 MBytes
[  5]  37.00-38.00  sec  83.8 MBytes   703 Mbits/sec    0   1.78 MBytes
[  5]  38.00-39.00  sec  86.2 MBytes   724 Mbits/sec    0   1.78 MBytes
[  5]  39.00-40.00  sec  86.2 MBytes   723 Mbits/sec    0   1.78 MBytes
[  5]  40.00-41.00  sec  86.2 MBytes   724 Mbits/sec    0   1.78 MBytes
[  5]  41.00-42.00  sec  87.5 MBytes   734 Mbits/sec    0   1.78 MBytes
[  5]  42.00-43.00  sec  86.2 MBytes   724 Mbits/sec    0   1.78 MBytes
[  5]  43.00-44.00  sec  82.5 MBytes   692 Mbits/sec    0   1.78 MBytes
[  5]  44.00-45.00  sec  61.2 MBytes   514 Mbits/sec   21   1.33 MBytes
[  5]  45.00-46.00  sec  67.5 MBytes   566 Mbits/sec    0   1.40 MBytes
[  5]  46.00-47.00  sec  71.2 MBytes   598 Mbits/sec    0   1.45 MBytes
[  5]  47.00-48.00  sec  72.5 MBytes   608 Mbits/sec    0   1.48 MBytes
[  5]  48.00-49.00  sec  72.5 MBytes   608 Mbits/sec    0   1.50 MBytes
[  5]  49.00-50.00  sec  75.0 MBytes   629 Mbits/sec    0   1.51 MBytes
[  5]  50.00-51.00  sec  73.8 MBytes   617 Mbits/sec    0   1.52 MBytes
[  5]  51.00-52.00  sec  75.0 MBytes   631 Mbits/sec    0   1.52 MBytes
[  5]  52.00-53.00  sec  76.2 MBytes   639 Mbits/sec    0   1.55 MBytes
[  5]  53.00-54.00  sec  76.2 MBytes   640 Mbits/sec    0   1.59 MBytes
[  5]  54.00-55.00  sec  80.0 MBytes   670 Mbits/sec    0   1.62 MBytes
[  5]  55.00-56.00  sec  80.0 MBytes   672 Mbits/sec    0   1.66 MBytes
[  5]  56.00-57.00  sec  81.2 MBytes   681 Mbits/sec    0   1.69 MBytes
[  5]  57.00-58.00  sec  82.5 MBytes   692 Mbits/sec    0   1.73 MBytes
[  5]  58.00-59.00  sec  83.8 MBytes   703 Mbits/sec    0   1.76 MBytes
[  5]  59.00-60.00  sec  88.8 MBytes   744 Mbits/sec    0   1.78 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec  4.68 GBytes   670 Mbits/sec   86             sender
[  5]   0.00-60.00  sec  4.68 GBytes   670 Mbits/sec                  receiver

iperf Done.
  • aj_potcaj_potc Member

    I just tested HostHatch Chicago -> HostHatch New York, and I was able to average 1.04 Gbits/sec during a 60-second iperf test. A big improvement!

    The opposite direction (HostHatch New York -> HostHatch Chicago) was a good bit slower: 300 Mbits/sec.

  • EasyCompany251EasyCompany251 Member
    edited February 2022

    Think I may have spoken too soon.....starts out good...but still falls well below even 100 Mbps over a 60 second time frame.

    Early Sunday afternoon Chicago HostHatch -> BUYVM NY

    root@localhost:~# iperf3 -c  HOSTHATCH -R -t 60
Connecting to host HOSTHATCH, port 5201
Reverse mode, remote host HOSTHATCH is sending
[  5] local BUYVM port 54350 connected to HOSTHATCH port 5201
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  36.2 MBytes   304 Mbits/sec
[  5]   1.00-2.00   sec  29.9 MBytes   251 Mbits/sec
[  5]   2.00-3.00   sec  21.0 MBytes   176 Mbits/sec
[  5]   3.00-4.00   sec  11.9 MBytes  99.8 Mbits/sec
[  5]   4.00-5.00   sec  9.60 MBytes  80.6 Mbits/sec
[  5]   5.00-6.00   sec  8.77 MBytes  73.5 Mbits/sec
[  5]   6.00-7.00   sec  9.99 MBytes  83.8 Mbits/sec
[  5]   7.00-8.00   sec  11.6 MBytes  97.6 Mbits/sec
[  5]   8.00-9.00   sec  12.6 MBytes   106 Mbits/sec
[  5]   9.00-10.00  sec  12.6 MBytes   106 Mbits/sec
[  5]  10.00-11.00  sec  5.05 MBytes  42.4 Mbits/sec
[  5]  11.00-12.00  sec  4.37 MBytes  36.7 Mbits/sec
[  5]  12.00-13.00  sec  5.06 MBytes  42.5 Mbits/sec
[  5]  13.00-14.00  sec  3.27 MBytes  27.4 Mbits/sec
[  5]  14.00-15.00  sec  3.49 MBytes  29.2 Mbits/sec
[  5]  15.00-16.00  sec  3.03 MBytes  25.4 Mbits/sec
[  5]  16.00-17.00  sec  2.73 MBytes  22.9 Mbits/sec
[  5]  17.00-18.00  sec  3.93 MBytes  33.0 Mbits/sec
[  5]  18.00-19.00  sec  5.48 MBytes  45.8 Mbits/sec
[  5]  19.00-20.00  sec  6.56 MBytes  55.1 Mbits/sec
[  5]  20.00-21.00  sec  4.12 MBytes  34.5 Mbits/sec
[  5]  21.00-22.00  sec  4.13 MBytes  34.7 Mbits/sec
[  5]  22.00-23.00  sec  5.29 MBytes  44.4 Mbits/sec
[  5]  23.00-24.00  sec  6.08 MBytes  51.0 Mbits/sec
[  5]  24.00-25.00  sec  5.87 MBytes  49.3 Mbits/sec
[  5]  25.00-26.00  sec  5.87 MBytes  49.3 Mbits/sec
[  5]  26.00-27.00  sec  6.27 MBytes  52.6 Mbits/sec
[  5]  27.00-28.00  sec  7.56 MBytes  63.4 Mbits/sec
[  5]  28.00-29.00  sec  5.84 MBytes  49.0 Mbits/sec
[  5]  29.00-30.00  sec  4.09 MBytes  34.3 Mbits/sec
[  5]  30.00-31.00  sec  5.46 MBytes  45.8 Mbits/sec
[  5]  31.00-32.00  sec  6.64 MBytes  55.7 Mbits/sec
[  5]  32.00-33.00  sec  7.66 MBytes  64.3 Mbits/sec
[  5]  33.00-34.00  sec  6.57 MBytes  55.1 Mbits/sec
[  5]  34.00-35.00  sec  4.82 MBytes  40.4 Mbits/sec
[  5]  35.00-36.00  sec  3.00 MBytes  25.1 Mbits/sec
[  5]  36.00-37.00  sec  3.55 MBytes  29.8 Mbits/sec
[  5]  37.00-38.00  sec  4.83 MBytes  40.5 Mbits/sec
[  5]  38.00-39.00  sec  6.30 MBytes  52.9 Mbits/sec
[  5]  39.00-40.00  sec  7.40 MBytes  62.1 Mbits/sec
[  5]  40.00-41.00  sec  4.88 MBytes  41.0 Mbits/sec
[  5]  41.00-42.00  sec  4.23 MBytes  35.5 Mbits/sec
[  5]  42.00-43.00  sec  5.44 MBytes  45.6 Mbits/sec
[  5]  43.00-44.00  sec  5.18 MBytes  43.4 Mbits/sec
[  5]  44.00-45.00  sec  6.27 MBytes  52.6 Mbits/sec
[  5]  45.00-46.00  sec  5.11 MBytes  42.8 Mbits/sec
[  5]  46.00-47.00  sec  5.18 MBytes  43.5 Mbits/sec
[  5]  47.00-48.00  sec  6.64 MBytes  55.7 Mbits/sec
[  5]  48.00-49.00  sec  6.07 MBytes  50.9 Mbits/sec
[  5]  49.00-50.00  sec  6.25 MBytes  52.5 Mbits/sec
[  5]  50.00-51.00  sec  4.81 MBytes  40.4 Mbits/sec
[  5]  51.00-52.00  sec  5.15 MBytes  43.2 Mbits/sec
[  5]  52.00-53.00  sec  3.59 MBytes  30.1 Mbits/sec
[  5]  53.00-54.00  sec  3.60 MBytes  30.2 Mbits/sec
[  5]  54.00-55.00  sec  4.89 MBytes  41.0 Mbits/sec
[  5]  55.00-56.00  sec  6.43 MBytes  54.0 Mbits/sec
[  5]  56.00-57.00  sec  5.06 MBytes  42.4 Mbits/sec
[  5]  57.00-58.00  sec  4.40 MBytes  36.9 Mbits/sec
[  5]  58.00-59.00  sec  4.72 MBytes  39.6 Mbits/sec
[  5]  59.00-60.00  sec  6.06 MBytes  50.8 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-60.00  sec   426 MBytes  59.5 Mbits/sec  1273             sender
[  5]   0.00-60.00  sec   423 MBytes  59.1 Mbits/sec                  receiver

iperf Done.

    BuyVM NY -> HostHatch Chicago averages over 700 Mbps over a 60 second time frame.

    root@localhost:~# iperf3 -c  45.45.216.152 -t 20
Connecting to host 45.45.216.152, port 5201
[  5] local 198.98.56.60 port 54342 connected to 45.45.216.152 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  75.3 MBytes   632 Mbits/sec    1   3.58 MBytes
[  5]   1.00-2.00   sec  82.5 MBytes   692 Mbits/sec    0   3.58 MBytes
[  5]   2.00-3.00   sec  85.0 MBytes   713 Mbits/sec    0   3.58 MBytes
[  5]   3.00-4.00   sec  81.2 MBytes   682 Mbits/sec    0   3.58 MBytes
[  5]   4.00-5.00   sec  83.8 MBytes   703 Mbits/sec    0   3.58 MBytes
[  5]   5.00-6.00   sec  85.0 MBytes   713 Mbits/sec    0   3.58 MBytes
[  5]   6.00-7.00   sec  85.0 MBytes   713 Mbits/sec    0   3.58 MBytes
[  5]   7.00-8.00   sec  83.8 MBytes   703 Mbits/sec    0   3.58 MBytes
[  5]   8.00-9.00   sec  87.5 MBytes   734 Mbits/sec    0   3.58 MBytes
[  5]   9.00-10.00  sec  83.8 MBytes   702 Mbits/sec    0   3.58 MBytes
[  5]  10.00-11.00  sec  83.8 MBytes   703 Mbits/sec    0   3.58 MBytes
[  5]  11.00-12.00  sec  86.2 MBytes   724 Mbits/sec    0   3.58 MBytes
[  5]  12.00-13.00  sec  85.0 MBytes   713 Mbits/sec    0   3.58 MBytes
[  5]  13.00-14.00  sec  86.2 MBytes   723 Mbits/sec    0   3.58 MBytes
[  5]  14.00-15.00  sec  83.8 MBytes   703 Mbits/sec    0   3.58 MBytes
[  5]  15.00-16.00  sec  78.8 MBytes   661 Mbits/sec    0   3.58 MBytes
[  5]  16.00-17.00  sec  85.0 MBytes   713 Mbits/sec    0   3.58 MBytes
[  5]  17.00-18.00  sec  83.8 MBytes   703 Mbits/sec    0   3.58 MBytes
[  5]  18.00-19.00  sec  86.2 MBytes   724 Mbits/sec    0   3.58 MBytes
[  5]  19.00-20.00  sec  82.5 MBytes   692 Mbits/sec    0   3.58 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-20.00  sec  1.63 GBytes   702 Mbits/sec    1             sender
[  5]   0.00-20.00  sec  1.63 GBytes   702 Mbits/sec                  receiver

iperf Done.

    Anybody else run some iperfs recently for their Chicago HostHatch servers?

  • aj_potcaj_potc Member

    The results seem highly variable on the route.

    My previous test sending data from Chicago out to HostHatch NY is now running much slower (around 300 Mbits/sec). But if I test to another server I have in the NY area, it's saturating the 1 Gbit link.

    Inbound to Chicago is the real issue. I can't push more than about 50-70 Mbit to HH Chicago from any New York location I try.

  • EasyCompany251EasyCompany251 Member

    @aj_potc said: Inbound to Chicago is the real issue. I can't push more than about 50-70 Mbit to HH Chicago from any New York location I try.

    Seems I have the exact opposite issue. Going out of HostHatch Chicago cannot break 60 Mbps. Going into HostHatch Chicago - can exceed 600 Mbps.

  • aj_potcaj_potc Member

    @EasyCompany251 said:
    Seems I have the exact opposite issue. Going out of HostHatch Chicago cannot break 60 Mbps. Going into HostHatch Chicago - can exceed 600 Mbps.

    That is indeed odd! I'm testing from three different NY-area servers, and consistently get pretty good inbound speeds from HostHatch Chicago, but totally lousy outbound.

  • yoursunnyyoursunny Member, IPv6 Advocate

    HostHatch Chicago storage from Nexril Dallas:

    • IPv4 ingress: 339Mbps
    • IPv4 egress: 408Mbps
    • IPv6 ingress: 644Mbps
    • IPv6 egress: 715Mbps
    $ iperf3 -c 193.29.63.xxx -u -b 900M -t 60
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-60.00  sec  6.29 GBytes   900 Mbits/sec  0.000 ms  0/4661544 (0%)  sender
[  5]   0.00-60.02  sec  2.37 GBytes   339 Mbits/sec  0.036 ms  2902612/4658183 (62%)  receiver

$ iperf3 -c 193.29.63.xxx -u -b 900M -t 60 -R
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-60.02  sec  2.86 GBytes   409 Mbits/sec  0.000 ms  0/2120872 (0%)  sender
[  5]   0.00-60.00  sec  2.85 GBytes   408 Mbits/sec  0.040 ms  6693/2120191 (0.32%)  receiver

$ iperf3 -c 2605:4840:3:xxxx::1 -u -b 900M -t 60
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-60.00  sec  6.29 GBytes   900 Mbits/sec  0.000 ms  0/4726829 (0%)  sender
[  5]   0.00-60.02  sec  4.50 GBytes   644 Mbits/sec  0.133 ms  1340894/4726496 (28%)  receiver

$ iperf3 -c 2605:4840:3:xxxx::1 -u -b 900M -t 60 -R
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-60.03  sec  5.03 GBytes   720 Mbits/sec  0.000 ms  0/3783927 (0%)  sender
[SUM]  0.0-60.0 sec  607 datagrams received out-of-order
[  5]   0.00-60.00  sec  4.99 GBytes   715 Mbits/sec  0.015 ms  26227/3780233 (0.69%)  receiver

    HostHatch Chicago storage from WebHorizon New York (ShockHosting Piscataway NJ):

    • IPv4 ingress: 390Mbps
    • IPv4 egress: 474Mbps
    • IPv6 ingress: 446Mbps
    • IPv6 egress: 825Mbps
    $ iperf3 -c 193.29.63.xxx -u -b 900M
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec   821 MBytes   689 Mbits/sec  0.000 ms  0/594711 (0%)  sender
[  5]   0.00-10.06  sec   390 MBytes   325 Mbits/sec  0.046 ms  310514/592722 (52%)  receiver

$ iperf3 -c 193.29.63.xxx -u -b 900M -R
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.06  sec   481 MBytes   401 Mbits/sec  0.000 ms  0/348005 (0%)  sender
[SUM]  0.0-10.1 sec  11521 datagrams received out-of-order
[  5]   0.00-10.00  sec   474 MBytes   398 Mbits/sec  0.177 ms  3615/347059 (1%)  receiver

$ iperf3 -c 2605:4840:3:xxxx::1 -u -b 900M
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.00  sec   462 MBytes   387 Mbits/sec  0.000 ms  0/339121 (0%)  sender
[  5]   0.00-10.06  sec   446 MBytes   372 Mbits/sec  0.030 ms  11229/338991 (3.3%)  receiver

$ iperf3 -c 2605:4840:3:xxxx::1 -u -b 900M -R
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-10.07  sec   949 MBytes   791 Mbits/sec  0.000 ms  0/696801 (0%)  sender
[SUM]  0.0-10.1 sec  117183 datagrams received out-of-order
[  5]   0.00-10.00  sec   825 MBytes   692 Mbits/sec  0.006 ms  88441/694309 (13%)  receiver
  • EasyCompany251EasyCompany251 Member
    edited February 2022

    @yoursunny said

    Try just plain old TCP. Rsync uses SSH which is generally TCP.

  • yoursunnyyoursunny Member, IPv6 Advocate

    @EasyCompany251 said:

    @yoursunny said

    Try just plain old TCP. Rsync uses SSH which is generally TCP.

    TCP is not a reliable reflection of L3 network performance.
    You should always measure with UDP.

  • TimboJonesTimboJones Member

    @yoursunny said:

    @EasyCompany251 said:

    @yoursunny said

    Try just plain old TCP. Rsync uses SSH which is generally TCP.

    TCP is not a reliable reflection of L3 network performance.
    You should always measure with UDP.

    You need both to get more information on the problem at hand.

  • Daniel15Daniel15 Veteran

    YABS for $70/year (60GB storage, 8GB RAM + extra 2GB for two year payment) VPS in Los Angeles:

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2021-12-28                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Sun 06 Feb 2022 03:51:23 PM PST

Basic System Information:
---------------------------------
Processor  : AMD EPYC 7443P 24-Core Processor
CPU cores  : 3 @ 2844.654 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ❌ Disabled
RAM        : 9.7 GiB
Swap       : 975.0 MiB
Disk       : 53.8 GiB

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 301.00 MB/s  (75.2k) | 3.76 GB/s    (58.8k)
Write      | 301.79 MB/s  (75.4k) | 3.78 GB/s    (59.1k)
Total      | 602.80 MB/s (150.7k) | 7.55 GB/s   (118.0k)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 9.03 GB/s    (17.6k) | 9.02 GB/s     (8.8k)
Write      | 9.51 GB/s    (18.5k) | 9.62 GB/s     (9.3k)
Total      | 18.55 GB/s   (36.2k) | 18.64 GB/s   (18.2k)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed
                |                           |                 |
Clouvider       | London, UK (10G)          | 261 Mbits/sec   | 560 Mbits/sec
Online.net      | Paris, FR (10G)           | 357 Mbits/sec   | 743 Mbits/sec
WorldStream     | The Netherlands (10G)     | busy            | 397 Mbits/sec
WebHorizon      | Singapore (400M)          | 238 Mbits/sec   | 504 Mbits/sec
Clouvider       | NYC, NY, US (10G)         | 673 Mbits/sec   | 1.46 Gbits/sec
Velocity Online | Tallahassee, FL, US (10G) | 4.08 Gbits/sec  | 505 Mbits/sec
Clouvider       | Los Angeles, CA, US (10G) | 1.85 Gbits/sec  | 5.68 Gbits/sec
Iveloz Telecom  | Sao Paulo, BR (2G)        | 272 Mbits/sec   | 966 Mbits/sec

iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed
                |                           |                 |
Clouvider       | London, UK (10G)          | 1.41 Gbits/sec  | 363 Mbits/sec
Online.net      | Paris, FR (10G)           | 4.50 Gbits/sec  | 440 Mbits/sec
WorldStream     | The Netherlands (10G)     | 1.14 Gbits/sec  | 344 Mbits/sec
WebHorizon      | Singapore (400M)          | 359 Mbits/sec   | 331 Mbits/sec
Clouvider       | NYC, NY, US (10G)         | 2.99 Gbits/sec  | 1.01 Gbits/sec
Clouvider       | Los Angeles, CA, US (10G) | 1.71 Gbits/sec  | 5.17 Gbits/sec

Geekbench 5 Benchmark Test:
---------------------------------
Test            | Value
                |
Single Core     | 1218
Multi Core      | 3392
Full Test       | https://browser.geekbench.com/v5/cpu/12626902
  • Daniel15Daniel15 Veteran
    edited February 2022

    Does anyone know if HostHatch intentionally changed from GiB (1 GiB = 1024 MiB) to GB (1GB = 1000MB) for these NVMe VPSes? sudo fdisk -l /dev/vda on their older VPSes show an exact number of GiB - a 60GB offer would have 60GiB space, ie 64424509440 bytes. However, on one of the new VPSes a 60GB disk is only 55.88GiB (59995324416 bytes), meaning it's 6.875% smaller. Only a sample size of 1 so I'm not sure if this is consistently the case.

    I know hard drive manufacturers use decimal bytes rather than binary bytes, but HostHatch used to always use binary bytes...

  • cybertechcybertech Member

    @Daniel15 said:
    Does anyone know if HostHatch intentionally changed from GiB (1 GiB = 1024 MiB) to GB (1GB = 1000MB) for these NVMe VPSes? sudo fdisk -l /dev/vda on their older VPSes show an exact number of GiB - a 60GB offer would have 60GiB space, ie 64424509440 bytes. However, on one of the new VPSes a 60GB disk is only 55.88GiB (59995324416 bytes), meaning it's 6.875% smaller. Only a sample size of 1 so I'm not sure if this is consistently the case.

    I know hard drive manufacturers use decimal bytes rather than binary bytes, but HostHatch used to always use binary bytes...

    yes i did ask, it is the case now.

    took over a 1TB STO storage and it came with 931 GiB.

    on that note, how's the STO storage users, any issues on your end? I have high IOWait on my VPS that affects single file upload speeds.

This discussion has been closed.