OK, I feel a Community Forum thread coming on! I'll start one later if no one else has.

IDNet 40/10 Mainly wireless, some wired.

12/7/2011 1:02 PM GMT 37.50 Mb/s 8.10 Mb/s 15 ms Maidenhead
12/7/2011 12:22 AM GMT 37.42 Mb/s 8.10 Mb/s 15 ms London
12/7/2011 12:21 AM GMT 37.41 Mb/s 8.10 Mb/s 15 ms London
12/7/2011 12:20 AM GMT 37.44 Mb/s 8.25 Mb/s 15 ms Newbury
12/7/2011 12:18 AM GMT 37.33 Mb/s 8.07 Mb/s 15 ms Maidenhead
11/5/2011 12:28 AM GMT 37.45 Mb/s 7.17 Mb/s 32 ms Skipton
10/28/2011 8:36 PM GMT 37.77 Mb/s 8.25 Mb/s 19 ms Manchester
10/28/2011 8:36 PM GMT 37.72 Mb/s 8.20 Mb/s 25 ms Lancaster
10/28/2011 8:35 PM GMT 37.45 Mb/s 6.70 Mb/s 17 ms Liverpool
10/28/2011 8:34 PM GMT 37.40 Mb/s 8.34 Mb/s 19 ms Manchester

In reply to a post by kasg:

I think you already know mine but sig gives results of test just done (just over 33 meg). Other testers (except BT) give from 1-2Mb higher. It should be higher, and has been in the past, I used to get over 36 on TBB and I don't know where the missing megs have gone! I'm still on maximum sync/profile and the maximum Plusnet profile of "37Mb"

If you want to see missing megabits in action...take a look at my speedtest tracking in my signature

But that's on Infinity, and you haven't got a full sync . Nice of you to have let me have them on IDNet though.

In reply to a post by kasg:

OK, I feel a Community Forum thread coming on! I'll start one later if no one else has.

Done - http://community.plus.net/forum/index.php/topic,1022...

Re Adam Walker's "I can also see we've raised this with our suppliers. I'll chase it up now". I assume he means BT Wholesale, in which case they are almost certainly nothing to do with it. Their profile is set at 38717. It has to be that Plusnet have got it wrong internally.

Edited by RobertoS (Mon 06-Feb-12 11:48:09)

In reply to a post by camieabz:

The '2/2/12s ' refers to those affected by the Plusnet problems of said date.

It's a date? Doh!

In reply to a post by kasg:

What kind of "semi-interested" response have you had?

It got mentioned quite a while ago, with a response that showed they'd checked their traffic management profiles, and all was well. But that was about it.

However, my latest reports got some response - they were passed up to the main networking & FTTC trial guy, who is handling it. It isn't a high priority, I suspect.

And TBH, once I get a fast session, I don't particularly want to lose it... so I stop testing things at that point.

Take a look at this thread

In reply to a post by RobertoS:

I gather that's the 40/10 trial.

Well, yes - but the original FTTC trial nearly a year ago, not the "mini" one that appears to be happening right now.

Can you remember if download was as good on 40/2? I'm wondering if something in the settings for your line could be giving a "Line speed" of the full 38717, (maybe 38700 there), sometimes reverting to the 40/2 setting of 37Mbps after the re-syncs/new seessions you mention. That would account for the difference, and the new PPP going back to the trial settings.

Back at the start, I was on 40/2 for 3 days - but the line was suffering from packet loss at the time, so wasn't easy to tell until DLM slowed it down - at which point I can't give you the answer.

What I can say is that when sync was 36Mbps-ish, profile 34800, I didn't see these kind of 2Mbps jumps/dips in speedtest results: Then it was a very consistent 33.6Mbps result.

But maybe I didn't connect enough times?

The *only* reason that I detected the problem was when the modem auto-synced on 31st October to pick up 17a (and DLM started afresh). I was back at 40Mbps, without interleaving and without packet loss. Download speeds were the fast 37.5Mbps... which lasted 2 days until I caused my own resync. I was then on a slow connection, and couldn't budge it....

Then 2 weeks later came another auto-sync, as DLM put in interleaving, but left the speed at 40. Again, I ended up on a fast connection... and then I knew something was up.

Subsequently, I've been able to trigger fast connections through router re-connections and through modem re-syncs, but it is still rarer than hen's teeth.

And, obviously, carried through the behaviour onto an entirely new line.

I don't think it is anything to do with the original 40/2 setting though.

In reply to a post by RobertoS:

Well we all know that the IP Profile is 38717, and that on ADSL2+ with the new WBC DLM PN now set the line speed to the "100" below, so I think it's a simple error and no-one in the system has the clout to challenge it.

Your suggestion is plausible, but gives a figure above the BT one, which would be incorrect. Pointless even.

The PN profile setting for my line has been at "37Mb" since the day I swapped to fibre - and has stayed at that even when DLM slowed the line down. Both of those predate the recent ADSL2+ profile changes.

And, obviously, it has stayed at 37Mb whether I get a fast session or a slow one.

While the profile is named "37Mb", I don't think it is limited to that, or wrongly limits things to "35Mbps". Indeed there is an old setting of "20Mb" on the same page that really means "unlimited" (I guess it was, in ADSL2+ days) - this setting was used on the original FTTC trial (and FTTP trial) before a better-named profile could be set up on the management system.

I also think the setting is static: once set manually(as part of the fibre install process), it stays there. The reason I believe this is that, for 2 weeks of the house move, we reverted to an ADSL2+ connection while waiting for OR to come out. The setting stayed at 37Mb throughout, no matter what sync the ADSL modem got.

I think the name of "37Mb" was chosen for the same reason that they chose "up to 20Mb" for ADSL2+ lines: management of expectations. It gives people a better idea of the speed they can realistically get after the most-hidden overheads are removed.