Download via your hfs server link = .5 MB/s
Download via your ftp to my ftp = 1.6 MB/s
Thanks for the results! It may have been just "a fluke". Or it may actually be that HFS has a limitation. Or it may be that the web browser has a limitation (for example,
Chromium). Both FileZilla and HFS are running on my computer in the
same conditions. I swear by FileZilla myself and use it for
reference (the buffer size is a very extreme example and not necessarily "correct"). FileZilla can also push gigabit speeds on LAN on Pentium-4 grade hardware. 1.6 MB/s looks about right.
Problem with FileZilla and "users" is that sometimes FTP isn't accessible for them. They try PORT mode with local IPs, request weird directories because they can't parse the file listing, have problems with special characters in file names, and so on. Or they "distrust" an FTP server. This is where a webserver comes in.
I am getting 127 ms to you today, but the value was around 145 when I looked at it on the day the test was carried out. I am in Latvia, which is approximately 10 ms from kst5-speedtest-1.tele2.net (note that the main address is AnyCasted, but by default resolves to kst5 for me). My path towards Verizon goes through "retn.net" and "ntt.net".
C:\>tracert 108.53.107.XXX
Tracing route to pool-108-53-107-XXX.nwrknj.fios.verizon.net [108.53.107.XXX]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.j7nh [192.168.15.254]
2 <1 ms 2 ms <1 ms 10.91.104.254
3 <1 ms <1 ms <1 ms te-2401-2-72-94.balticom.lv [82.193.72.94]
4 <1 ms <1 ms <1 ms balticom-193-69-199.balticom.lv [82.193.69.199]
5 <1 ms <1 ms <1 ms ge-te-s5-64-254.balticom.lv [82.193.64.254]
6 4 ms 1 ms 1 ms te1-2.501.tv.riga.globalcom.lv [85.254.1.135]
7 3 ms 33 ms 1 ms ae0-504.rt.rtc.rix.lv.retn.net [87.245.242.25]
8 29 ms 28 ms 30 ms ae0-4.rt.irx.fkt.de.retn.net [87.245.233.74]
9 29 ms 29 ms 29 ms 213.198.77.213
10 * 35 ms 32 ms ae-2.r20.frnkge04.de.bb.gin.ntt.net [129.250.5.217]
11 150 ms 119 ms 114 ms ae-7.r22.asbnva02.us.bb.gin.ntt.net [129.250.3.20]
12 120 ms 115 ms 115 ms ae-44.r06.asbnva02.us.bb.gin.ntt.net [129.250.6.113]
13 123 ms 130 ms 122 ms ae-0.verizonbusiness.asbnva02.us.bb.gin.ntt.net [129.250.8.34]
14 * * * Request timed out.
15 * * * Request timed out.
16 126 ms 127 ms 127 ms pool-108-53-107-XXX.nwrknj.fios.verizon.net [108.53.107.XXX]
OOKLA opens 6 to 8 connections. You can observe that if you run TcpView. If you go to FileZilla Client's settings and set "maximum simultaneous transfers" to 8, and queue this many large files, the speeds would match up. And you would be able to set the length of the test by your own choosing.
20 Mbit to Australia cannot be possible over 1 connection. No way.
Tele2 are all close to me. The site says that, "TCP windows have been slightly tweaked to support higher throughput."
You could also ask over at the TestMy.net forums I linked. They seem to have the expertise but only seem to concern with web browsers, which have too many variables in them. I have shared my experience with FTP/FileZilla and Tele2 over there.
I'm very pleased with the tele2 service. I was also able to benchmark my FileZilla Server by initiating a FXP transfer between it and their box. No other site offers this flexibility.
I'm looking forward to a follow up when you get time.
