speed test size on fast connections

speed test size on fast connections 16MB is bit small for 30-120mb connections, 16mb is fine for ADSL as you hardly ever get more then 5mb (500KB/s)

FTTC or virgin media 30-120mb service as it can complete it in less then 3 to 0.8 seconds so the speed result at the end can end up been to slow when its not, could do with an tick box for fast broadband connections (test file 50MB? so its 2-3x the size of the norm test that think broadband do)

----
ok i see what it is doing its randomly picking an file size that explained why some tests are better last one was 23mb then 16 then 68 and so on, just the smaller then 20-50MB tests will not get an good avg speed result on high speed connections

Edited by leexgx (Mon 12-Mar-12 05:30:58)

how about using these? the ThinkBroadband tester links to them.

http://www.thinkbroadband.com/download/

Also - saying you hardly ever get more than 5 meg from ADSL is a horrible generalisation.

i also think i posted this in the incorrect place as well

around where i service computers this exchange cover wide area so unless VM is around its norm 0.6-6mb ADSL speeds unless your quite close to it as the exchange is in the town center Warrington

Our speedtester will use varying sizes of files and is generally a bigger payload than other testers (am referring to the non-android tester here), and I think maximum is around 150MB.

i meant this post to be related to the java speed test app on the site

it could do with an Max muti thread test at the start to work out what the max download speed is before doing the single thread download (to work out an size for the test file)

isposure seems to get around 50.30mb consistently but that mite be muti threaded (thinkbroadband Broadband Quality Monitor ping jumps up at the time when it runs)

Edited by leexgx (Mon 12-Mar-12 10:04:49)

While multi threading at start might help in picking a bigger filesize.

We have seen it use large file sizes on VM 50 Meg lines, and even at single thread we know we can go a lot faster than 50 Meg.Also if you TCP stack takes a long time to ramp its RWIN we can show slower results than other testers, but then users see this in real results too.

Multithread will arrive on the tester at some point, a case of resources versus sleep

just that the current tests its hit or miss if you get an 16mb or 90mb file, as an 16mb test is not realistic on an 30-100mb connection as it can be done before the test can avg it out right

i can see that your servers can give out 51mb most likely even 100mb maybe as the tbbmeter when doing 50mb tests tends to max my line out

even now just using the site its not matching what my network card says (5.3% utilization on 1gb port)

Web browsing is very unlikely to tax a 50 Meg connection, particularly one that is not very graphics heavy

Our tester was certified as fine for testing 50 Meg lines a long time ago, and since then we've increased payload to cope with 100Meg, and we see people with connections of 100 Meg or more daily.