2

Ookla's speedtest gives the option of running their speed test using a single-threaded or multi-threaded connection.

According to this source:

Most large downloads [over the web] and streaming services operate over a single connection to the server, so it makes sense to measure the throughput available over a single connection. Personally this is my preferred test when comparing ISPs even though it may not show what the connection is capable of with multiple simultaneous connections.

Why would single-threaded connections be the preferred choice when comparing different ISP speeds? I'm guessing to test the quality of an ISP's connection, right?

Friedrich Bauer
  • 51
  • 1
  • 3

1 Answers1

0

Many ISPs prioritise Ookla traffic, completely messing up any attempt at direct comparison. The best you can do is test both methods & average them.

Try DSLReports instead. It does use different metrics & one could claim it's a 'better' objective test - but more importantly, most ISPs seem to have forgotten to prioritise it, so it can be more accurate as a real-world comparison. It will also test for bufferbloat.

enter image description here

Clicking the Results gives a far more comprehensive analysis.

No affiliation.

*As mentioned in comments, don't confuse the naming of 'multi-threading' with that normally associated with CPU threads. This is about multiple simultaneous connections.
Also note that bufferbloat is usually of far greater significance than a flat-out speed test, under real-world conditions.

Tetsujin
  • 47,296
  • 8
  • 108
  • 135
  • OK, but many tests give you the option of picking between a multi-threaded or single-threaded connection. What I'd like to know is when you should pick one over the other. I'd also like to know why someone would want to use a single-threaded connection to compare different ISPs. – Friedrich Bauer Mar 10 '21 at 16:55
  • Threading as a local CPU feature is unlikely to affect the network throughput by much, unless your computer is "slow" in comparison to the network hardware. – Hannu May 14 '23 at 06:55
  • @Hannu - Though they use the term 'thread' they're not talking about CPU task threads but multiple simultaneous connections. – Tetsujin May 14 '23 at 07:02
  • 1
    Then the OP needs to be made aware of the difference. Using the same term for more than one feature us unfortunate, even if it is suiting. Maybe add that to your answer? – Hannu May 14 '23 at 07:06
  • I'm not sure there was any confusion anyway. My answer was really a frame challenge. SpeedTest is pretty useless other than to test your last mile.It no longer shows the threading option; it's no longer Flash-based. Such as Test.my also call the tests single- & multi-threading, so it's not like we're going to fix the entire interwebz nomenclature from here… and last of all, bufferbloat is usually a far bigger issue these days, with so many households trying to squeeze everything down wifi rather than use 'proper' ethernet. – Tetsujin May 14 '23 at 07:22
  • 2
    @Hannu - I've added a bit, put more emphasis on bufferbloat too, & updated my DSLReports pic, to better reflect the current status. – Tetsujin May 14 '23 at 07:27