then those results are useless, please print the single threaded. This is important andrew, its been made clear the issues affect single threaded performance. I hope you are as keen to show the single threaded tests as you were the multi.

Edited by Chrysalis (Tue 07-Jul-15 22:11:21)

That was httpx6 in the blog

Need more data so more registrered users doing speed tests basically

The beta web single one might get used once I've had time to look and plusnet users confirm it behaves the same way as the flash, need confirmation due to the way traffic management operates

Do you have any individuals' data that tally or contradict the graphs?

I ran this one but it only did one download test which is single or multi threaded?

http://labs.thinkbroadband.com/speedtest/?site=omega
http://www.thinkbroadband.com/speedtest/results.html...

The main difference will be on the upload test, on html5 it uses the browser specified sendbuffer, which e.g. firefox is the network.tcp.sendbuffer variable.

Flash will use the OS send buffer.

Edited by Chrysalis (Wed 08-Jul-15 00:50:05)

Since I joined Plusnet I have had very consistent speedtests, with almost completely flat lines on the graph, e.g.
http://www.thinkbroadband.com/speedtest/results.html...

When I was on Infinity the graph jumped up and down like mad, especially the HTTPx1 test.
Consistency in the Plusnet test is probably helped as I am on 40/20, synced at 50 with available speeds well above 70.
I had 80/20 on Infinity, so the bouncing HTTPx1 test still usually averaged above 40.

I just tried the other test at
http://labs.thinkbroadband.com/speedtest/?site=omega
and the upload on that zigzags like mad, though keeping pretty much to the same overall speed
http://www.thinkbroadband.com/speedtest/results.html...

Probably not really significant, and maybe just due to different sampling/smoothing on the result data

Yes different methodology for the upload so will never be as flat as the flash on that side

Also that was the multi thread you ran as the site parameter was curtailed.

Edited by MrSaffron (Wed 08-Jul-15 09:24:34)

As the graph shows two sets of download figures it did the HTTPx1 test, as I said the speed test result image needs tweaking to reflect this beta.

The vast majority probably don't want another 12 seconds added to the duration of the speed test, so single threading may end up being something you have to choose as part of diagnostic testing etc

As you know in large datasets there are always individuals that contradict the overall results. If everyone was a model connection we could just speedtest one user from each ISP and publish a big table 100+ ISP long.

In reply to a post by MrSaffron:

Ok it was on the todo list already, so here is a beta for a version of the new test that uses just a single thread

http://labs.thinkbroadband.com/speedtest/?site=omega...

Looks the same as the new web version, but slightly different text on start page, and if you share the graph at the end you can spot difference as it shows a tbbx1 result. The page that does the graph drawing will need some tweaking in the future, but as hinted elsewhere waiting on some other stuff.

These tests are logged under a specific version, hence the random string, so if the consensus is that this does not work then we can exclude from the monthly results. If it does work then after a decent period of data collection will look at how adding a single thread run before or after a multiple thread run.

My own connection non-PlusNet has been showing single thread problems today, so a good day test/code this version. Blames Wimbledon and people streaming while at their office desk.

11am on Zen

http://www.thinkbroadband.com/speedtest/results.html...

I have noticed it seems to be servers located in London. I get the same results on speedtest.net from London servers but go elsewhere and it's fine.

http://www.speedtest.net/my-result/4489332711

Edited by deleted (Wed 08-Jul-15 11:17:57)