Kitz Forum

Broadband Related => FTTC and FTTP Issues => Topic started by: jaydub on December 28, 2017, 10:36:44 PM

Title: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 28, 2017, 10:36:44 PM
I moved to Fibre with Pulse8 in November 2016 and had single thread speed problems almost immediately.  After some lobbying by Adam at Pulse8 with TTB, the root cause was eventually identified and I had a period of pretty solid single thread speeds.

This deteriorated with the advent of the non-Flash based TTB tester in May this year, which I eventually traced down to my AV, Eset Cyber Security Pro, impacting the single thread results.  this was rectified by swapping to KIS which appears to have a negligible effect on the speed test.

For most of the rest of my time with Pulse8, the single thread speeds were fairly solid although there was always a slight undercurrent of poorer results.  After 12 months I decided to migrate to Aquiss.  The result was very good single thread speeds out of the working day, but their business prioritisation and/or the Entanet node I was connected to running a bit hot, resulted in very variable results throughout the day.

Martin Pitt at Aquiss very graciously made the offer for me to migrate away without penalty and in mid-December I migrated to IDNet on their Fluid Data TTB backhaul.

Since then speeds have been quite variable without their being any obvious pattern to it.  Out of 5 consecutive tests I might get one really good one, one poor one and three middling ones regardless of when in the day I am testing.

I attach a scatter chart for the last three months of my TTB tests.

In general terms the IDNet connection is giving me worse single thread results than either Aquiss or Pulse8 (see figures below).

           IDNet   Aquiss   Pulse8
         
Mean     59.7     60.8     64.2
Median   63.6     69.5     66.9

As the distribution is somewhat skewed the median figures are probably more significant than the mean.

I reliably sync at 80/20 with a 9dB margin and my connection passes the normal line tests that ISPs do (as confirmed by both Aquiss and IDNet).

My MDWS results are available under jaydub and seem fairly unremarkable although my Quiet Line graph is noisier than ideal.

I am in discussions with IDNet about where to go from here, but would welcome your thoughts.

A few questions from my end:
Title: Re: Ongoing issues with Single Thread Speeds
Post by: burakkucat on December 28, 2017, 11:08:37 PM
IDNet are offering to move the backhaul service from TTB.

From TTB to whom?
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 28, 2017, 11:32:33 PM
From TTB to whom?
The last email I had from them suggested BTW, which has confused me as I thought they either used Fluid Data or Zen for backhaul services and consequently BTW only came into play if your cabinet wasn't connected to a Zen PoP, which ours is.

I have sought clarification from IDNet.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: burakkucat on December 28, 2017, 11:52:23 PM
I see, thank you. That is a little puzzling.  ???

I think that most of us who take note of "what is going on" will be aware that A&A use both BTW and TTB for backhaul . . . with the latter being slightly more favoured than the former.

Not intending to be provocative but I have to ask the question --

Does the problem with single thread speeds actually stop you making the use of the provided broadband service connecting you to the Internet?
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 29, 2017, 12:16:09 AM
I see, thank you. That is a little puzzling.  ???

I think that most of us who take note of "what is going on" will be aware that A&A use both BTW and TTB for backhaul . . . with the latter being slightly more favoured than the former.

Not intending to be provocative but I have to ask the question --

Does the problem with single thread speeds actually stop you making the use of the provided broadband service connecting you to the Internet?

Being absolutely honest, with IDnet the answer is no.

But the scientist/engineer in me wants to understand why, if others get single thread speeds that match their multithread speeds within 1Mbps or so, I don't.

And there's the tight fisted Yorkshire git in me, that wonders why I am paying more than I was with Pulse8 to get less speed.

Ultimately there might be an element of 'you live and learn by your mistakes' going on here, but I would like to use this as a learning opportunity to understand where the issues might be and what, if anything, I can do about them.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: burakkucat on December 29, 2017, 12:30:23 AM
As a fellow scientist, I can now say that I understand your logic.  :)
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 29, 2017, 12:51:18 AM
As a fellow scientist, I can now say that I understand your logic.  :)

 ;D
And a little element of a dog with a bone.  ;)
Title: Re: Ongoing issues with Single Thread Speeds
Post by: Chrysalis on December 29, 2017, 01:03:01 AM
my single tbb matches the multi yes, if its variable 24/7 regardless of peak hours imo it means one off following

1 transit problem between isp and tbb
2 congestion thats persistent all day, if it were this it would still be noticeably worse at peak so unlikely
3 misconfigured traffic shaping at ISP
4 local problem in your network
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 29, 2017, 10:47:52 AM
my single tbb matches the multi yes, if its variable 24/7 regardless of peak hours imo it means one off following

1 transit problem between isp and tbb
2 congestion thats persistent all day, if it were this it would still be noticeably worse at peak so unlikely
3 misconfigured traffic shaping at ISP
4 local problem in your network

Thanks, Chrysalis.

So following this logic through:

1 Unlikely because other IDNet customers get their single thread speeds matching their multi.
2 No obvious time of day pattern with the results.  No sign of congestion on my BQM.
3 Unlikely because other IDNet customers get their single thread speeds matching their multi.
4  All things are possible.  Oldish master socket fitted with Mk3 faceplate filter fitted on Engineer install in November 2016. Testing taking place on an iMac on a dedicated browser with no add ons.  Testing from the master socket with a dangly filter makes no difference.  I've swapped out the router also tried changing Ethernet and modem cables with no apparent difference. 

I would like it to local TBH, as that would be a simple fix.  The only thing I haven't ruled out is that it's the iMac itself causing issues, but at the moment I don't have any other hardware I can directly cable into the router.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 29, 2017, 01:37:39 PM
As a further update:

The only bit of my connection I hadn't swapped out was the iMac itself.

I've just dome some testing from my son's laptop on an ethernet connection to the router and can see no significant difference in the test results.

It was what i expected, but did just want to rule out that it was the Mac causing the issues.

I've also asked a neighbour to run me some results off to see whether he sees anything similar.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: Chrysalis on December 30, 2017, 06:29:43 AM
Can you stick in a rescue OS USB in the imac, boot off it, so you can speedtest using a different OS at its defaults?

Various images come with a browser that can be used so can run speedtests etc.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on December 31, 2017, 12:10:39 AM
Can you stick in a rescue OS USB in the imac, boot off it, so you can speedtest using a different OS at its defaults?

Various images come with a browser that can be used so can run speedtests etc.
Have struggled with creating a rescue disk off High Sierra, but have created a bootable install disk and reloaded the OS from there.

No noticeable difference, as expected since a Win 10 laptop gives similar results.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 03, 2018, 08:38:49 PM
IDNet are going to change the backhaul from TTB to BTW in an effort to isolate the LLU equipment at the exchange being the source of the issue.  I seem to have done enough to convince them that it isn't a local issue.

Having had fibre on two TTB backhaul providers (Pulse8 and IDNet) and one BTW (Aquiss) over the last few months, Aquiss were the only ones that provided consistent single thread download speeds (albeit only out of business prioritisation hours), so this may work.

If consulted, I'd have rather tried Zen, but I understand their logic.  Time will tell whether it is right or not.  The backhaul transfer takes place on Jan 16th.

After that, I think I'll either feel vindicated or think I ought put up and shut up.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: PhilipD on January 06, 2018, 12:06:54 PM
Hi

Just to add I've not had maximum throughput via Uno (which use TalkTalk) for many, many months on the single thread speed test, regardless of the time day or night, I usually get around 60-64Mbps on the single thread test, with the multi-thread test always ~74Mbps. I know when you first posted about this and I replied I was getting maximum on both types of test, but at some point that changed, although nothing my end has changed.

However playing about with TCP Optimizer https://www.speedguide.net/downloads.php I can improve the single thread speeds back up to almost match the the multi-thread speed, so I don't think it is something being deliberately throttled by TalkTalk, just some interaction between Windows (10 in my case) automatic network settings just not hitting an optimal match against TalkTalk and the site it's connecting to.  This may explain why some speed tests are okay and others are not.

Edit:  if I test here https://testmy.net/results and use the single thread speed test option I get consistently > 73Mbps, it's only ThinkBroadband's single threaded part of the test that is impacted, which I think was your original issue?  I think the problem is with Thinkbroadband and how the test is routed or network parameters and there isn't really any problem at all with the speeds, just the test.
 

Regards

Phil




Title: Re: Ongoing issues with Single Thread Speeds
Post by: Weaver on January 06, 2018, 12:20:20 PM
Didn't AA have a similar experience with TT at some point? I can't remember.

Would AA suit you? They are very keen on performance monitoring.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 06, 2018, 01:31:51 PM
Hi

Just to add I've not had maximum throughput via Uno (which use TalkTalk) for many, many months on the single thread speed test, regardless of the time day or night, I usually get around 60-64Mbps on the single thread test, with the multi-thread test always ~74Mbps. I know when you first posted about this and I replied I was getting maximum on both types of test, but at some point that changed, although nothing my end has changed.

However playing about with TCP Optimizer https://www.speedguide.net/downloads.php I can improve the single thread speeds back up to almost match the the multi-thread speed, so I don't think it is something being deliberately throttled by TalkTalk, just some interaction between Windows (10 in my case) automatic network settings just not hitting an optimal match against TalkTalk and the site it's connecting to.  This may explain why some speed tests are okay and others are not.

Edit:  if I test here https://testmy.net/results and use the single thread speed test option I get consistently > 73Mbps, it's only ThinkBroadband's single threaded part of the test that is impacted, which I think was your original issue?  I think the problem is with Thinkbroadband and how the test is routed or network parameters and there isn't really any problem at all with the speeds, just the test.
 

Regards

Phil

Hi Phil,

Interesting that you are seeing a reduction in single thread speeds with Uno.  There's another IDNet customer on TBB who has been moved from a BTW backhaul with evening congestion to a TTB backhaul and seeing something akin to what I am seeing.  He's had his fill of IDNet and has just placed a migration order with Uno, so may give him a heads up of what you are seeing at Uno.

I've not done any TestMy.Net testing but did run their auto tests for a couple of days after joining IDNet.  As you can see from the attached graphs, the speeds were generally better, but there were some definite blips as well.  I might just try running a few manual tests back to back to see how consistent they are one after another.

Out of interest, have you tried running TestMy.Net in multithread mode to just the London server.  It just won't run smoothly for me.

Uno used to have a single thread tester, but they seem to have taken that off line.  I found that a useful reference point in the past, so it's a shame it has gone.

I'm running off a Mac, so speedguide.net tweaking is not an option for me.  I have validated my TBB results with my son's Win10 laptop, so fairly certain it's not the Mac at fault here.

Thanks,

Jon
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 06, 2018, 01:40:58 PM
Didn't AA have a similar experience with TT at some point? I can't remember.

Would AA suit you? They are very keen on performance monitoring.

They did.  At the beginning of last year IIRC.  Pulse8 had something similar when I was with them, which affected certain gateways and was unrelated to the AA issue.  That was fixed after about a month of investigation.

I'm not mad keen on going to AA for a couple of reasons:
1)  I've just paid for 12 months up front with IDNet and not willing to write that money off, unless I can negotiate a refund.
2)  I've still got an adult child at home and the other one threatening to come back at some stage, so not sure I really want to go on a limited bandwidth product offering.

They do remain an option for the future though.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: Chrysalis on January 06, 2018, 03:04:15 PM
For me the small niche providers arent what they used to be and I now consider risky, they dont have the benefit of large swarms of customers able to absorb heavy users like the large isps do and as such I actually now thing visible contention is more likely on smaller provider, AAISP I have as an exception tho as their managing director has always made a point of AAISP never been the bottleneck.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 06, 2018, 03:14:25 PM
I might just try running a few manual tests back to back to see how consistent they are one after another.

Done.  Results attached.  I then ran 5 TBB tests and got single thread results of: 71, 50.2, 67.5, 68.8 & 67.7 Mbps.  Better than I have been seeing off TBB, but not as good or consistent as TestMy.Net.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: PhilipD on January 07, 2018, 10:57:01 AM
Hi

The question is, are we just testing the tester now?

There is something going on with TalkTalk I think and as Uno get handed off to Daisy this I would think points more towards their back haul. 

This is a test just now, not too bad for the single thread test but it the speed used to always been on parity with the multi-threaded speed, so it isn't' constantly around 10% less that I've often seen recently.  So probably congestion rather than a deliberate throttling, it's hard to complain as it is sold as a contended service, and it never gets any worse than a 10% reduction, and of course if a second person in the household is doing something online or we are streaming and downloading, we will be maxing out the line no problem. 

I wonder if this is some QOS setting on their network and is by design to reserve bandwidth for TalkTalks TV service?

(https://www.thinkbroadband.com/_assets/speedtest/button/1515322006658716655.png)

Regards

Phil


Title: Re: Ongoing issues with Single Thread Speeds
Post by: bilbokitz on January 18, 2018, 11:35:38 PM

Would the single thread be the limiting factor for an openvpn client connecting to a vpn provider from within my network?
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jelv on January 19, 2018, 08:44:45 AM
You are questioning why you are not getting the speed you were getting from Pulse8. The question not asked (and not possible to answer without trying it) is what speed would you be getting now with Pulse8 if you were still with them? Would it have also degraded?
Title: Re: Ongoing issues with Single Thread Speeds
Post by: Weaver on January 19, 2018, 09:50:38 AM
Btw, this has been said before. AA publish their own congestion figures (http://control.aa.net.uk/congestion.cgi). I don't know if anyone else does. There used to be a detailed table of packets dropped - don't know where that went. Perhaps it is because they are using some Cisco core switches and routers now instead of all Firebrick kit, until the forthcoming high speed Bricks become available.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 19, 2018, 10:26:21 AM
You are questioning why you are not getting the speed you were getting from Pulse8. The question not asked (and not possible to answer without trying it) is what speed would you be getting now with Pulse8 if you were still with them? Would it have also degraded?

That in itself is an interesting question, but one that is likely to remain unanswered.

I guess the more fundamental question is whether there was actually any value in changing, especially as I am now paying more per month than with Pulse8.

By way of an update, this Tuesday IDNet transferred my backhaul from TTB to BTW, and although the results aren't absolutely amazing they have resulted in a significant improvement (see attached IDNet scatter plot).

The first couple of days were pretty good, but am seeing some degradation in single thread speeds since yesterday (see attached IDNet BTW scatter plot).

In terms of a straight forward figures analysis, the answer at the moment is that IDNet on a BTW backhaul are still doing better than Pulse8 did in my last few weeks with them.


          IDNet (BTW)      IDNet (TTB)      Aquiss       Pulse8
Mean        69.4                   59.6              60.8          64.2
Median     71.1                   63.3              69.5          66.9
Std Dev     5.5                   10.0              17.5            9.4

What I'm really struggling to understand is the variation in TBB single thread speeds on consecutive tests.  I always do them in packets of 3 tests and the most recent gave me 72.5, 59.7 & 42.3 Mbps.

Does anybody else see that level of variation?  Any guesses why back to back tests should be so different?

Title: Re: Ongoing issues with Single Thread Speeds
Post by: Ixel on January 19, 2018, 10:49:01 AM
Btw, this has been said before. AA publish their own congestion figures (http://control.aa.net.uk/congestion.cgi). I don't know if anyone else does. There used to be a detailed table of packets dropped - don't know where that went. Perhaps it is because they are using some Cisco core switches and routers now instead of all Firebrick kit, until the forthcoming high speed Bricks become available.

I don't think that table shows up unless there's actually a problem. I'm pretty sure I recall seeing such a table at some point in the last few months.

That in itself is an interesting question, but one that is likely to remain unanswered.

I guess the more fundamental question is whether there was actually any value in changing, especially as I am now paying more per month than with Pulse8.

By way of an update, this Tuesday IDNet transferred my backhaul from TTB to BTW, and although the results aren't absolutely amazing they have resulted in a significant improvement (see attached IDNet scatter plot).

The first couple of days were pretty good, but am seeing some degradation in single thread speeds since yesterday (see attached IDNet BTW scatter plot).

In terms of a straight forward figures analysis, the answer at the moment is that IDNet on a BTW backhaul are still doing better than Pulse8 did in my last few weeks with them.


          IDNet (BTW)      IDNet (TTB)      Aquiss       Pulse8
Mean        69.4                   59.6              60.8          64.2
Median     71.1                   63.3              69.5          66.9
Std Dev     5.5                   10.0              17.5            9.4

What I'm really struggling to understand is the variation in TBB single thread speeds on consecutive tests.  I always do them in packets of 3 tests and the most recent gave me 72.5, 59.7 & 42.3 Mbps.

Does anybody else see that level of variation?  Any guesses why back to back tests should be so different?



That level of variation does seem a bit large compared to the variation I see on my connection. I'm seeing a variation of no larger than 10 megabits typically (download speed maxing out at around 60 megabits).

This is a recent test I did (via the TTB backhaul):
(https://www.thinkbroadband.com/_assets/speedtest/button/1516358581545376955.png)

Bear in mind I'm using QoS (fq_codel) on my EdgeRouter.

There's some occasions on other tests where it can be a larger variation though, but when I monitor my own network it's usually when another device is also using the internet for that moment. My ping would normally be much lower but DLM kicked in recently and I don't know what exactly happened but I guess downstream MTBE exceeded the threshold. I've noticed I'm getting large bursts of FEC errors on my DrayTek again, so I'm guessing my original fault is returning (or has become a bit more noticeable now?). I might put the HG612 or Zyxel back on, capped though, to mainly check if the Hlog and QLN have changed... but that's another story.
Title: Re: Ongoing issues with Single Thread Speeds
Post by: jaydub on January 19, 2018, 01:03:49 PM
I don't think that table shows up unless there's actually a problem. I'm pretty sure I recall seeing such a table at some point in the last few months.

That level of variation does seem a bit large compared to the variation I see on my connection. I'm seeing a variation of no larger than 10 megabits typically (download speed maxing out at around 60 megabits).

This is a recent test I did (via the TTB backhaul):
(https://www.thinkbroadband.com/_assets/speedtest/button/1516358581545376955.png)

Bear in mind I'm using QoS (fq_codel) on my EdgeRouter.

There's some occasions on other tests where it can be a larger variation though, but when I monitor my own network it's usually when another device is also using the internet for that moment. My ping would normally be much lower but DLM kicked in recently and I don't know what exactly happened but I guess downstream MTBE exceeded the threshold. I've noticed I'm getting large bursts of FEC errors on my DrayTek again, so I'm guessing my original fault is returning (or has become a bit more noticeable now?). I might put the HG612 or Zyxel back on, capped though, to mainly check if the Hlog and QLN have changed... but that's another story.

The variation is getting worse and the poorer results slower and more frequent.  The last couple of tests have been 70.4, 31.7 & 17.5 Mbps and then a couple of hours later 70.7, 28 & 34.6.  Time to speak to IDNet support again.