![]() ![]() ![]() |
|
Lorenceo: Pretty sure that their capacity on the SCC is to Australia only. Snap are peering directly at Equinix Sydney now, which eliminates a lot of Telstra's odd routing.
Bandwidth to the rest of the world however seems to either go through Telstra Global, Alter.net or Cognetco.
quakeguy: With the stock Linux kernel settings you can run into limits in TCP single-threaded
Here, try a speedtest from my server: https://de.tw.net.nz/testfile
Straight wget: wget -O /dev/null --no-check-certificate https://de.tw.net.nz/testfile
(output to /dev/null - and don't check certificate because I'm cheap and can't afford a certificate ;-))
mercutio:quakeguy: With the stock Linux kernel settings you can run into limits in TCP single-threaded
Here, try a speedtest from my server: https://de.tw.net.nz/testfile
Straight wget: wget -O /dev/null --no-check-certificate https://de.tw.net.nz/testfile
(output to /dev/null - and don't check certificate because I'm cheap and can't afford a certificate ;-))
quakeguy... https compresses null bytes, you need random data. or to use http.
quakeguy: With the stock Linux kernel settings you can run into limits in TCP single-threaded throughput, even in modern (3.2-3.5) kernels (For reference, Ubuntu 12.04 uses kernel 3.2).
The main limitation you hit is that window size becomes a throughput constraint at latencies higher than about 150ms. I don't have the exact figure, so don't quote me on this...
Since most speedtest.net servers will be running Linux, and some administrators of these servers will know about this tweak, you will get random results which range from quite good to quite poor, depending on what tweaks (if any) have been done.
I have adjusted a server I run in Germany to compensate for this. Basically, you can tweak the maximum TCP window and buffer sizes in the sysctl.conf on most Linux distributions. I run Ubuntu 12.04LTS with kernel 3.2.0-32-generic.
The NIC on my server is connected at 100mbit/sec.
Here's what I've done:
[appended to /etc/sysctl.conf]
net.core.wmem_max=12582912
net.core.rmem_max=12582912
net.ipv4.tcp_rmem= 10240 87380 12582912
net.ipv4.tcp_wmem= 10240 87380 12582912
net.ipv4.tcp_window_scaling = 1
net.ipv4.tcp_timestamps = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_no_metrics_save = 1
net.core.netdev_max_backlog = 5000
Here, try a speedtest from my server: https://de.tw.net.nz/testfile
Straight wget: wget -O /dev/null --no-check-certificate https://de.tw.net.nz/testfile
(output to /dev/null - and don't check certificate because I'm cheap and can't afford a certificate ;-))
**Edit: You might want to note that a number of users immediately did simultaneous tests as soon as I posted this, and I only have 100mbit/sec of upload, so... run your test a few times :-)
quakeguy:mercutio:quakeguy: With the stock Linux kernel settings you can run into limits in TCP single-threaded
Here, try a speedtest from my server: https://de.tw.net.nz/testfile
Straight wget: wget -O /dev/null --no-check-certificate https://de.tw.net.nz/testfile
(output to /dev/null - and don't check certificate because I'm cheap and can't afford a certificate ;-))
quakeguy... https compresses null bytes, you need random data. or to use http.
Oh, does it? Hmm. Well, I've replaced testfile with random data now!
mercutio: ... so it appears there's an issue with downloading over your max speed, which can impact maximum rates obtained.
|
![]() ![]() ![]() |