Howdy, Stranger!

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


Lunanode -- Slow-ish Download Speeds in Toronto - Page 3
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.

Lunanode -- Slow-ish Download Speeds in Toronto

13

Comments

  • Thanks. I was 0.1% worried.

  • @rm_ said:

    cirrus_cloud said: Is anyone else having network issues in Lunanode.com's Toronto location? I got ~4 MB/s upload to the server on a 5 GB file.

    Maybe just the peering between your ISP and Cogent is overloaded. Try running a benchmark script such as https://k4y5.github.io/ServerBench/ to see if it's a general problem with the download speed, or how many of the test locations are affected.

    This seems the most likely.

  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @jsg said:

    @cirrus_cloud said:
    I didn't want to bother them having to reply to a ticket with their network being somewhat slow for someone who spends a nominal amount of money there each month, although I've been there for 2.5+ years now. And I know there's others here who use Lunanode who might have some input since I moved to the Toronto location more recently from Montreal.

    Well done! Why waste valuable ticket bytes at your provider when there is the Low End Ticket system.

    Re. your problems, my suggestion is to continue your analysis and to keep switching around your VMs. Plus you should install and test no less than 6 different linux distros, some with and some without systemd. Finally, also try different shells! I've seen cases where a network was tested on tuesday by someone using bash and again a week later by someone using pdksh and the results were quite different! (Not to complicate things but you might also want to check what linker flags were used when building them shells!)

    I moved my VM from Montreal to Toronto. I don't think it has anything to do with network settings or other magic. I haven't touched anything like that.

  • @Janevski said:
    I don't know...
    It could be crappy upload speed due to your ISP being congested, due to something in between being congested, or provider downlink congestion.

    It could also be low HDD write speed on your VPS.

    If you're using something encrypted like ssh, it may as well be cpu bottleneck.

    But it may as well be MTU and MSS misconfiguration on your end.

    Or it may be abnormally low tcp buffers...

    And also it could be about 666 other different things. Investigate.

    I've never had any issues with hitting 100+ mbps upload with Verizon and sustaining it. But maybe it's the connection to Cogent.

    As for everything else, the only thing I think might be remotely the issue is the CPU with SSH. Even then, I'm pushing ~13-14 MB/s right now to the server (in bursts, not sustained), and only then is the CPU hitting 100% load. It's like 20% load at ~30 mbps. I have 1 core with Lunanode.

  • @eol said:
    Have you tried to turn it off and off again?

    Yes, I rebooted it from the get-go once I suspected something was an issue.

    Thanked by 2eol uptime
  • If your CPU can't handle SSH without puking, congraulations- you're on a VAXstation!

    That said, you've endured the huge amount of shitposts all over your thread and not even bothered to react. Good for you!

    If you're pushing 100% CPU with 13Mbps, you're probably on a HDD node with a deadlockline scheduler. Not much else to do but ask them to deal with noisy neighbors, deal with it, or move on.

  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @perennate said:

    smile said: let's be serious for a moment. where's @perennate ? This is an unacceptable ticket response time!

    Was skiing ^^

    @cirrus_cloud it sounds like there is a routing issue between Cogent and your ISP. If you open a ticket and give a remote IP that we can ping then we can look into it, although it's unlikely we can do much in the short term. If you ran into an issue in Montreal that made you want to switch to Toronto we could look into that as well.

    I didn't have any issues in Montreal. I just noticed that you guys recommended Toronto because there were more Ceph nodes than Montreal and Roubaix. Oh, and you had the deal recently, so I used it as an opportunity to move my volume to Toronto. I can give you my IP / open a ticket.

    Otherwise, I am getting ~14 MB/s uploading to the server off and on. Sometimes it drops back to like 2 MB/s, though.

  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @Letzien said:
    If your CPU can't handle SSH without puking, congraulations- you're on a VAXstation!

    That said, you've endured the huge amount of shitposts all over your thread and not even bothered to react. Good for you!

    If you're pushing 100% CPU with 13Mbps, you're probably on a HDD node with a deadlockline scheduler. Not much else to do but ask them to deal with noisy neighbors, deal with it, or move on.

    Let me check the CPU model / speed. But yes, I saw it hit 99% in htop at ~120 mbps (14 MB/s), which is my max upload anyway.

    Toronto:

    cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 42
    model name : Intel Xeon E312xx (Sandy Bridge)
    stepping : 1
    microcode : 0x1
    cpu MHz : 2899.998
    cache size : 4096 KB

    Toronto openssl speed rsa:

                  sign    verify    sign/s verify/s
    

    rsa 512 bits 0.000060s 0.000004s 16718.5 240662.2
    rsa 1024 bits 0.000178s 0.000011s 5604.0 87367.1
    rsa 2048 bits 0.001266s 0.000038s 789.7 26500.5
    rsa 4096 bits 0.009010s 0.000139s 111.0 7180.1

    Montreal:

    cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 60
    model name : Intel Core Processor (Haswell, no TSX)
    stepping : 1
    microcode : 0x1
    cpu MHz : 2593.990
    cache size : 4096 KB
    physical id : 0
    siblings : 1
    core id : 0
    cpu cores : 1
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 13
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl cpuid tsc_known_freq pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm invpcid_single pti tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 avx2 smep bmi2 erms invpcid xsaveopt
    bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
    bogomips : 5187.98
    clflush size : 64
    cache_alignment : 64
    address sizes : 40 bits physical, 48 bits virtual

    Montreal openssl speed rsa:

                  sign    verify    sign/s verify/s
    

    rsa 512 bits 0.000069s 0.000005s 14554.5 209310.3
    rsa 1024 bits 0.000202s 0.000012s 4953.5 86650.2
    rsa 2048 bits 0.000827s 0.000038s 1209.5 26357.2
    rsa 3072 bits 0.004166s 0.000090s 240.0 11104.1
    rsa 4096 bits 0.011053s 0.000139s 90.5 7207.0
    rsa 7680 bits 0.073285s 0.000472s 13.6 2120.0
    rsa 15360 bits 0.456818s 0.001862s 2.2 537.0

                  sign    verify    sign/s verify/s
    

    rsa 512 bits 0.000065s 0.000005s 15481.0 206534.6
    rsa 1024 bits 0.000203s 0.000013s 4914.2 76829.1
    rsa 2048 bits 0.000915s 0.000039s 1092.5 25625.6
    rsa 3072 bits 0.004148s 0.000083s 241.1 12036.0
    rsa 4096 bits 0.009803s 0.000146s 102.0 6859.8
    rsa 7680 bits 0.074148s 0.000482s 13.5 2076.7
    rsa 15360 bits 0.483810s 0.001920s 2.1 521.0

    I'm sitting at 37-55% cpu in Montreal while I upload to it at 14 MB/s. Note: Toronto is Ubuntu 16 I think. Montreal is a fresh install of Ubuntu 18. As you can see, I the tests are slightly different (Montreal goes up to 15360 bits for the tests).

  • Some one rang the Yeti Assassins?

  • I just tried a 4-core VM in Toronto, and CPU definitely should not have been an issue. I am getting similar network speeds with it. I'm getting below 20 mbps (2 MB/s) upload to it at times.

    Thanked by 1uptime
  • There's something unsettling going on. Montreal, unless hosted on a 10 year old laptop, has a different CPU/hardware model, and I can't think of any specific reason why other than to artificially limit things.

  • rm_rm_ IPv6 Advocate, Veteran
    edited February 2019

    cirrus_cloud said: I am getting similar network speeds with it. I'm getting below 20 mbps (2 MB/s) upload to it at times.

    You keep posting and posting again, but still couldn't simply run the test and show the results.

    rm_ said: Try running a benchmark script such as https://k4y5.github.io/ServerBench/ to see if it's a general problem with the download speed, or how many of the test locations are affected.

    Maybe indeed like the first reply said, you're not interested in diagnosing the issue, but just lonely and want to talk.

  • @rm_ said:

    cirrus_cloud said: I am getting similar network speeds with it. I'm getting below 20 mbps (2 MB/s) upload to it at times.

    You keep posting and posting again, but still couldn't simply run the test and show the results.

    rm_ said: Try running a benchmark script such as https://k4y5.github.io/ServerBench/ to see if it's a general problem with the download speed, or how many of the test locations are affected.

    Maybe indeed like the first reply said, you're not interested in diagnosing the issue, but just lonely and want to talk.

    I'm not sure what your test is going to prove. Lunanode / perennate already said on this thread it's probably something between my ISP and Cogent. I created a ticket, and they saw some packet loss that could be causing some throttling.

    I ran the script, and it's been running for 2+ hours. The speedtests don't take into account a really slow connection to one of those servers, so when the connection is 200 KB/s it takes forever to download 100 MB. I'll run another script if you send me something that doesn't involve a hard-coded speedtest.

  • @cirrus_cloud if you ever decide to read an intro book on networking; you will get an answer.

  • @smile said:
    @cirrus_cloud if you ever decide to read an intro book on networking; you will get an answer.

    OK.

  • rm_rm_ IPv6 Advocate, Veteran
    edited February 2019

    cirrus_cloud said: I'm not sure what your test is going to prove. Lunanode / perennate already said on this thread it's probably something between my ISP and Cogent.

    If they did, then perhaps it can switch that from probably to certainly.

    cirrus_cloud said: I ran the script, and it's been running for 2+ hours. The speedtests don't take into account a really slow connection to one of those servers, so when the connection is 200 KB/s it takes forever to download 100 MB. I'll run another script if you send me something that doesn't involve a hard-coded speedtest.

    You can try this one: https://bench.sh/, it doesn't test as many of the Asian locations, which could have slow speeds for you.

  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @rm_ said:

    cirrus_cloud said: I'm not sure what your test is going to prove. Lunanode / perennate already said on this thread it's probably something between my ISP and Cogent.

    If they did, then perhaps it can switch that from probably to certainly.

    cirrus_cloud said: I ran the script, and it's been running for 2+ hours. The speedtests don't take into account a really slow connection to one of those servers, so when the connection is 200 KB/s it takes forever to download 100 MB. I'll run another script if you send me something that doesn't involve a hard-coded speedtest.

    You can try this one: https://bench.sh/, it doesn't test as many of the Asian locations, which could have slow speeds for you.

    I'll edit the other one and will remove the Singapore and Vilnius locations that were taking a long time.

  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @rm_ said:

    cirrus_cloud said: I'm not sure what your test is going to prove. Lunanode / perennate already said on this thread it's probably something between my ISP and Cogent.

    If they did, then perhaps it can switch that from probably to certainly.

    cirrus_cloud said: I ran the script, and it's been running for 2+ hours. The speedtests don't take into account a really slow connection to one of those servers, so when the connection is 200 KB/s it takes forever to download 100 MB. I'll run another script if you send me something that doesn't involve a hard-coded speedtest.

    You can try this one: https://bench.sh/, it doesn't test as many of the Asian locations, which could have slow speeds for you.

    I got rid of all of the really slow locations (some were like 200 KB/s):

    ./serverbench.sh

    CPU model : Intel Xeon E312xx (Sandy Bridge)
    Number of cores : 1
    CPU frequency : 2899.998 MHz
    Total amount of ram : 992 MB
    Total amount of swap : 0 MB
    System uptime : 3days, 2:37:54
    Load average : 0.01, 0.02, 0.00
    OS : Ubuntu 16.04.5 LTS
    Arch : x86_64 (64 Bit)

    Kernel : 4.4.0-142-generic

    Node Name IPv4 address Download Speed
    CacheFly 205.234.175.175 33.1MB/s
    Softlayer, Milan, IT 159.122.128.84 7.30MB/s
    Prometeus, Milan, IT 37.247.53.10 1.80MB/s
    Tele2, Riga, LV 90.130.74.113 2.15MB/s
    Server.LU, Luxembourg, LU 94.242.192.2 6.16MB/s
    Tele2, Frankfurt, DE 90.130.74.155 8.38MB/s
    Vultr, Frankfurt, DE 108.61.210.117 23.4MB/s
    Linode, Frankfurt, DE 139.162.130.8 17.2MB/s
    Softlayer, Frankfurt, DE 159.122.69.4 11.7MB/s
    Leaseweb, Frankfurt, DE 37.58.58.140 16.5MB/s
    DO, Frankfurt, DE 46.101.218.147 16.7MB/s
    Vultr, Paris, FR 108.61.209.127 18.6MB/s
    OVH, Gravelines, FR 5.196.90.200 2.92MB/s
    OVH, Strasbourg, FR 5.135.128.81 1.34MB/s
    OVH, Roubaix, FR 188.165.12.106 7.96MB/s
    Online.Net, Paris, FR 62.210.18.40 11.5MB/s
    Tele2, Amsterdam, NL 90.130.74.153 5.79MB/s
    Vultr, Amsterdam, NL 108.61.198.102 23.2MB/s
    DO 2, Amsterdam, NL 188.226.175.227 21.5MB/s
    DO 3, Amsterdam, NL 178.62.216.76 14.4MB/s
    Leaseweb, Amsterdam, NL 5.79.108.33 15.7MB/s
    i3d, Amsterdam, NL 213.163.76.135 13.4MB/s
    Vultr, London, UK 108.61.196.101 24.1MB/s
    DO, London, UK 46.101.44.214 14.8MB/s
    Linode, London, UK 176.58.107.39 15.6MB/s
    Softlayer, London, UK 5.10.97.132 13.4MB/s
    Softlayer, Mexico, MX 169.57.4.116 13.0MB/s
    Softlayer, Brazil, BR 169.57.128.148 4.32MB/s
    DO 1, NYC, USA 165.227.194.167 26.1MB/s
    DO 2, NYC, USA 192.241.184.88 28.8MB/s
    DO 3, NYC, USA 174.138.51.137 27.0MB/s
    Vultr, New Jersey, USA 108.61.149.182 28.4MB/s
    Linode, Newark, USA 50.116.57.237 26.4MB/s
    Vultr, Illinois, USA 107.191.51.12 31.3MB/s
    Vultr, Atlanta, USA 108.61.193.166 28.5MB/s
    Linode, Atlanta, USA 50.116.39.117 25.1MB/s
    Vultr, Miami, USA 104.156.244.232 30.1MB/s
    Vultr, Washington, USA 108.61.194.105 21.8MB/s
    Softlayer, Seattle, USA 67.228.112.250 18.5MB/s
    Leaseweb, Washington, USA 207.244.94.80 29.3MB/s
    Vultr, Dallas, USA 108.61.224.175 28.0MB/s
    Linode, Dallas, USA 50.116.25.154 24.0MB/s
    Softlayer, Dallas, USA 173.192.68.18 22.4MB/s
    Leaseweb, Dallas, USA 209.58.153.1 23.8MB/s
    Vultr, Los Angeles, USA 108.61.219.200 25.0MB/s
    DO, San Francisco, USA 165.227.29.84 18.0MB/s
    DO, San Francisco, USA 107.170.223.15 29.8MB/s
    Linode, Fremont, USA 50.116.14.9 17.2MB/s
    Leaseweb, San Francisco, USA 209.58.135.187 17.7MB/s
    DO, Toronto, CA 159.203.57.38 29.6MB/s
    OVH, Beauharnois, CA 192.99.19.165 8.42MB/s
    EastLink, Canada, CA 24.222.0.194 13.6MB/s

    Softlayer, Montreal, CA 169.54.124.180 17.7MB/s

    Node Name IPv6 address Download Speed
    Linode, Atlanta, GA 2600:3c02::4b 28.9MB/s
    Linode, Dallas, TX 2600:3c00::4b 17.8MB/s
    Linode, Newark, NJ 2600:3c03::4b 26.0MB/s

    Softlayer, Paris, FR 2a03:8180:1301:8::4

    I/O speed(1st run) : 276 MB/s
    I/O speed(2nd run) : 298 MB/s
    I/O speed(3rd run) : 298 MB/s
    Average I/O speed : 290.667 MB/s

    ./serverbench.sh

    CPU model : Intel Xeon E312xx (Sandy Bridge)
    Number of cores : 1
    CPU frequency : 2899.998 MHz
    Total amount of ram : 992 MB
    Total amount of swap : 0 MB
    System uptime : 3days, 2:58:24
    Load average : 1.84, 0.95, 0.54
    OS : Ubuntu 16.04.5 LTS
    Arch : x86_64 (64 Bit)

    Kernel : 4.4.0-142-generic

    Node Name IPv4 address Download Speed
    CacheFly 205.234.175.175 30.9MB/s
    Softlayer, Milan, IT 159.122.128.84 10.3MB/s
    Prometeus, Milan, IT 37.247.53.10 1.20MB/s
    Tele2, Riga, LV 90.130.74.113 8.29MB/s
    Server.LU, Luxembourg, LU 94.242.192.2 7.57MB/s
    Tele2, Frankfurt, DE 90.130.74.155 3.25MB/s
    Vultr, Frankfurt, DE 108.61.210.117 19.5MB/s
    Linode, Frankfurt, DE 139.162.130.8 21.3MB/s
    Softlayer, Frankfurt, DE 159.122.69.4 10.3MB/s
    Leaseweb, Frankfurt, DE 37.58.58.140 15.9MB/s
    DO, Frankfurt, DE 46.101.218.147 19.9MB/s
    Vultr, Paris, FR 108.61.209.127 23.4MB/s
    OVH, Gravelines, FR 5.196.90.200 2.86MB/s
    OVH, Strasbourg, FR 5.135.128.81 1.58MB/s
    OVH, Roubaix, FR 188.165.12.106 5.70MB/s
    Online.Net, Paris, FR 62.210.18.40 2.95MB/s
    Tele2, Amsterdam, NL 90.130.74.153 3.55MB/s
    Vultr, Amsterdam, NL 108.61.198.102 23.7MB/s
    DO 2, Amsterdam, NL 188.226.175.227 22.9MB/s
    DO 3, Amsterdam, NL 178.62.216.76 16.7MB/s
    Leaseweb, Amsterdam, NL 5.79.108.33 21.2MB/s
    i3d, Amsterdam, NL 213.163.76.135 6.09MB/s
    Vultr, London, UK 108.61.196.101 20.7MB/s
    DO, London, UK 46.101.44.214 23.0MB/s
    Linode, London, UK 176.58.107.39 14.7MB/s
    Softlayer, London, UK 5.10.97.132 11.2MB/s
    Softlayer, Mexico, MX 169.57.4.116 13.6MB/s
    Softlayer, Brazil, BR 169.57.128.148 8.33MB/s
    DO 1, NYC, USA 165.227.194.167 28.5MB/s
    DO 2, NYC, USA 192.241.184.88 27.2MB/s
    DO 3, NYC, USA 174.138.51.137 27.5MB/s
    Vultr, New Jersey, USA 108.61.149.182 29.9MB/s
    Linode, Newark, USA 50.116.57.237 27.4MB/s
    Vultr, Illinois, USA 107.191.51.12 30.5MB/s
    Vultr, Atlanta, USA 108.61.193.166 26.4MB/s
    Linode, Atlanta, USA 50.116.39.117 27.1MB/s
    Vultr, Miami, USA 104.156.244.232 29.0MB/s
    Vultr, Washington, USA 108.61.194.105 24.7MB/s
    Softlayer, Seattle, USA 67.228.112.250 8.23MB/s
    Leaseweb, Washington, USA 207.244.94.80 25.5MB/s
    Vultr, Dallas, USA 108.61.224.175 27.4MB/s
    Linode, Dallas, USA 50.116.25.154 23.6MB/s
    Softlayer, Dallas, USA 173.192.68.18 21.8MB/s
    Leaseweb, Dallas, USA 209.58.153.1 22.6MB/s
    Vultr, Los Angeles, USA 108.61.219.200 20.9MB/s
    DO, San Francisco, USA 165.227.29.84 22.2MB/s
    DO, San Francisco, USA 107.170.223.15 24.9MB/s
    Linode, Fremont, USA 50.116.14.9 21.8MB/s
    Leaseweb, San Francisco, USA 209.58.135.187 21.2MB/s
    DO, Toronto, CA 159.203.57.38 29.8MB/s
    OVH, Beauharnois, CA 192.99.19.165 6.89MB/s
    EastLink, Canada, CA 24.222.0.194 12.5MB/s

    Softlayer, Montreal, CA 169.54.124.180 19.2MB/s

    Node Name IPv6 address Download Speed
    Linode, Atlanta, GA 2600:3c02::4b 25.2MB/s
    Linode, Dallas, TX 2600:3c00::4b 26.9MB/s
    Linode, Newark, NJ 2600:3c03::4b 15.1MB/s

    Softlayer, Paris, FR 2a03:8180:1301:8::4

    I/O speed(1st run) : 262 MB/s
    I/O speed(2nd run) : 322 MB/s
    I/O speed(3rd run) : 132 MB/s
    Average I/O speed : 238.667 MB/s

    Thanked by 1uptime
  • @cirrus_cloud thanks muchly for doing the needful ...

    Noticing OVH and Softlayer are at the slow end of this pool - which does point to peering issues with cogent (which are likely due to cogent's business decisions and maybe not so likely to get resolved anytime soon, but who knows)

    I would be interested to see list of the ultra-slow ones you removed from the script altogether

  • rm_rm_ IPv6 Advocate, Veteran
    edited February 2019

    cirrus_cloud said: I got rid of all of the really slow locations (some were like 200 KB/s):

    So it looks mostly just fine to me. If you would also not fuck up the formatting entirely, and just post it with the <prе> </prе> tags.

  • @cirrus_cloud said:
    I got rid of all of the really slow locations (some were like 200 KB/s):

    Ah yeah.
    That's exactly how benchmarking works.
    Let's get rid of all the low numbers.
    All good.

    Thanked by 2AuroraZ imok
  • @uptime said:
    @cirrus_cloud thanks muchly for doing the needful ...

    Noticing OVH and Softlayer are at the slow end of this pool - which does point to peering issues with cogent (which are likely due to cogent's business decisions and maybe not so likely to get resolved anytime soon, but who knows)

    I would be interested to see list of the ultra-slow ones you removed from the script altogether

    I'll run it tonight with the slow ones included. Singapore, Japan, Australia, and one in Lithuania I think.

    Thanked by 2uptime eol
  • uptimeuptime Member
    edited February 2019

    That is quite the list of speedtests ... seems like most are fine from Toronto except a few which are really slow.

    Might be more useful to just do an mtr for the slow ones, no need to torture them with more speedtests unless somethings changed to test again. (Not suggesting you actually do any more unless it's interesting to you.)

    I did notice much better speed (full 100 mbits) to kimsufi in BHS last time I checked.

    I'm guessing the problem in general has to do with cogent's peering (business decisions), and the solution you've found is to use Montreal instead of Toronto. (I'm okay with the "good enough" cogent in Toronto so far, but am not currently using it enough to really notice problems if any.)

    Thanked by 1eol
  • imokimok Member
    edited February 2019

    I decided to run a test.

    Lunanode vs Hivelocity vs Virmach vs Hosthatch

    Looks fine.

    Thanked by 1uptime
  • My nuts itch. @3606202

    Thanked by 13606202
  • cirrus_cloudcirrus_cloud Member
    edited February 2019

    @eol said:

    @cirrus_cloud said:
    I got rid of all of the really slow locations (some were like 200 KB/s):

    Ah yeah.
    That's exactly how benchmarking works.
    Let's get rid of all the low numbers.
    All good.

    This is all of them. There are no 200 KB/s tests on here, so it's definitely better than when I first tried.

    ----------------------------------------------------------------------
    CPU model            : Intel Xeon E312xx (Sandy Bridge)
    Number of cores      : 1
    CPU frequency        : 2899.998 MHz
    Total amount of ram  : 992 MB
    Total amount of swap : 0 MB
    System uptime        : 3days, 23:24:15
    Load average         : 0.03, 0.02, 0.00
    OS                   : Ubuntu 16.04.5 LTS
    Arch                 : x86_64 (64 Bit)
    Kernel               : 4.4.0-142-generic
    ----------------------------------------------------------------------
    Node Name           IPv4 address        Download Speed
    CacheFly            205.234.175.175     31.6MB/s
    Vultr, Tokyo, JP        108.61.201.151      14.6MB/s
    Linode, Tokyo, JP       106.187.96.148      12.5MB/s
    DO, Bangalore, IN       139.59.80.215       7.98MB/s
    Softlayer, Chennai, IN      169.38.65.84        5.36MB/s
    Vultr, Singapore, SG        45.32.100.168       9.68MB/s
    DO, Singapore, SG       159.89.192.182      8.54MB/s
    Linode, Singapore, SG       139.162.23.4        9.17MB/s
    Softlayer, Singapore, SG    119.81.28.170       6.52MB/s
    Leaseweb, Singapore, SG     103.254.153.18      9.40MB/s
    Softlayer, HongKong, CN     119.81.130.170      6.51MB/s
    Leaseweb, HongKong, CN      43.249.36.49        13.2MB/s
    Vultr, Sydney, AUS      108.61.212.117      10.5MB/s
    Softlayer, Sydney, AUS      168.1.1.212     5.48MB/s
    Softlayer, Melbourne, AUS   168.1.65.244        4.55MB/s
    Tele2, Gothenberg, SE       90.130.74.151       11.6MB/s
    Tele2, Kista, SE        90.130.74.149       9.61MB/s
    Softlayer, Milan, IT        159.122.128.84      6.23MB/s
    Prometeus, Milan, IT        37.247.53.10        10.0MB/s
    Tele2, Riga, LV     90.130.74.113       9.02MB/s
    Tele2, Vilnius, LT      90.130.74.117       8.40MB/s
    Server.LU, Luxembourg, LU   94.242.192.2        16.3MB/s
    Tele2, Frankfurt, DE        90.130.74.155       12.4MB/s
    Vultr, Frankfurt, DE        108.61.210.117      20.8MB/s
    Linode, Frankfurt, DE       139.162.130.8       19.1MB/s
    Softlayer, Frankfurt, DE    159.122.69.4        12.8MB/s
    Leaseweb, Frankfurt, DE     37.58.58.140        24.6MB/s
    DO, Frankfurt, DE       46.101.218.147      19.5MB/s
    Vultr, Paris, FR        108.61.209.127      23.2MB/s
    OVH, Gravelines, FR     5.196.90.200        2.93MB/s
    OVH, Strasbourg, FR     5.135.128.81        1.46MB/s
    OVH, Roubaix, FR        188.165.12.106      9.37MB/s
    Online.Net, Paris, FR       62.210.18.40        13.3MB/s
    Tele2, Amsterdam, NL        90.130.74.153       12.3MB/s
    Vultr, Amsterdam, NL        108.61.198.102      24.9MB/s
    DO 2, Amsterdam, NL     188.226.175.227     23.3MB/s
    DO 3, Amsterdam, NL     178.62.216.76       18.7MB/s
    Leaseweb, Amsterdam, NL     5.79.108.33     25.1MB/s
    i3d, Amsterdam, NL      213.163.76.135      19.2MB/s
    Vultr, London, UK       108.61.196.101      23.6MB/s
    DO, London, UK      46.101.44.214       20.4MB/s
    Linode, London, UK      176.58.107.39       20.9MB/s
    Softlayer, London, UK       5.10.97.132     16.2MB/s
    Softlayer, Mexico, MX       169.57.4.116        7.62MB/s
    Softlayer, Brazil, BR       169.57.128.148      5.68MB/s
    DO 1, NYC, USA      165.227.194.167     29.3MB/s
    DO 2, NYC, USA      192.241.184.88      30.3MB/s
    DO 3, NYC, USA      174.138.51.137      30.5MB/s
    Vultr, New Jersey, USA      108.61.149.182      30.2MB/s
    Linode, Newark, USA     50.116.57.237       30.2MB/s
    Vultr, Illinois, USA        107.191.51.12       32.8MB/s
    Vultr, Atlanta, USA     108.61.193.166      32.3MB/s
    Linode, Atlanta, USA        50.116.39.117       30.4MB/s
    Vultr, Miami, USA       104.156.244.232     30.0MB/s
    Vultr, Washington, USA      108.61.194.105      27.7MB/s
    Softlayer, Seattle, USA     67.228.112.250      18.3MB/s
    Leaseweb, Washington, USA   207.244.94.80       31.6MB/s
    Vultr, Dallas, USA      108.61.224.175      31.4MB/s
    Linode, Dallas, USA     50.116.25.154       28.4MB/s
    Softlayer, Dallas, USA      173.192.68.18       20.8MB/s
    Leaseweb, Dallas, USA       209.58.153.1        24.2MB/s
    Vultr, Los Angeles, USA     108.61.219.200      27.4MB/s
    DO, San Francisco, USA      165.227.29.84       24.2MB/s
    DO, San Francisco, USA      107.170.223.15      17.7MB/s
    Linode, Fremont, USA        50.116.14.9     24.7MB/s
    Leaseweb, San Francisco, USA    209.58.135.187      26.4MB/s
    DO, Toronto, CA     159.203.57.38       31.8MB/s
    OVH, Beauharnois, CA        192.99.19.165       8.70MB/s
    EastLink, Canada, CA        24.222.0.194        13.6MB/s
    Softlayer, Montreal, CA     169.54.124.180      23.3MB/s
    ----------------------------------------------------------------------
    Node Name           IPv6 address        Download Speed
    Linode, Atlanta, GA     2600:3c02::4b       32.2MB/s
    Linode, Dallas, TX      2600:3c00::4b       30.2MB/s
    Linode, Newark, NJ      2600:3c03::4b       31.2MB/s
    Linode, Singapore, SG       2400:8901::4b       9.91MB/s
    Linode, Tokyo, JP       2400:8900::4b       11.0MB/s
    Softlayer, Paris, FR        2a03:8180:1301:8::4 12.7MB/s
    Softlayer, Tokyo, JP        2401:c900:1001:16::4    8.03MB/s
    ----------------------------------------------------------------------
    I/O speed(1st run) : 339 MB/s
    I/O speed(2nd run) : 451 MB/s
    I/O speed(3rd run) : 345 MB/s
    Average I/O speed  : 378.333 MB/s
    
    
    Thanked by 2eol uptime
  • @Letzien said:
    My nuts itch. @3606202

    Interesting.
    I thought you are female.

    Thanked by 13606202
  • @eol said:

    @Letzien said:
    My nuts itch. @3606202

    Interesting.
    I thought you are female.

    That's $30 extra.

    Thanked by 13606202
  • @Letzien said:

    @eol said:

    @Letzien said:
    My nuts itch. @3606202

    Interesting.
    I thought you are female.

    That's $30 extra.

    You don't even have a provider tag.

    https://www.lowendtalk.com/discussion/153228/rules-for-selling-on-lowendtalk-updated-04th-jan-2019/p1

    Thanked by 13606202
  • @eol said:

    @Letzien said:

    @eol said:

    @Letzien said:
    My nuts itch. @3606202

    Interesting.
    I thought you are female.

    That's $30 extra.

    You don't even have a provider tag.

    https://www.lowendtalk.com/discussion/153228/rules-for-selling-on-lowendtalk-updated-04th-jan-2019/p1

    The 30 bucks is just to cover processor fees; the service itself is free.

    Thanked by 13606202
Sign In or Register to comment.