Interleaving

Ted · Jan 19, 2009, 20:55:50

I asked IDnet to get BT to switch off interleaving this morning, which should happen within 24 hours.

When interleaving is switched off at the exchange does it automatically trigger a re-sync of the router?

I imagine it would, just wondering.

Simon · Jan 19, 2009, 21:29:38

Couldn't tell you, Ted, but I expect someone will.

Ted · Jan 19, 2009, 21:41:30

I think more than a few here have had it done, so someone will know, i'm sure.

Lance · Jan 19, 2009, 21:53:55

I had interleaving turned off a while back (although I've had it turned back on since), and from memory it didn't trigger a resync. I may well be wrong though!

The other thing to note is that the exchange hardware doesn't always remember the correct setting, so you may need to ask support to do it again in a few days. Normally though if it sticks for the first 24 hours, it'll be stuck for good!

g7pkf · Jan 19, 2009, 21:54:51

yes sort of, it does drop and come back but in the 2 times i have had it done it re-synced straight back to original setting

drummer · Jan 19, 2009, 21:59:01

I had interleaving turned off recently and the only thing that happened was the change of sync from 7616 to 8128.

According to my router's logs and RouterStats, I remained connected during the transition. Schweet.

g7pkf · Jan 19, 2009, 22:14:24

My router was obviously being as sensitive as usual, could also be the dslam is alcatel? that might be the differance

Ted · Jan 19, 2009, 22:20:14

Thanks people, i'll check in the morning, if its not showing Fastpath and a higher sync i'll reboot and go from there.

Lance · Jan 19, 2009, 23:06:02

The dslam way well make a difference, Dean. All i know about mine is that its some old marconi kit!

Ann · Jan 19, 2009, 23:42:36

I don't know what happened to mine with regard to resynching but I got interleaving turned off and got top speed for the whole weekend but on Monday it went clack and changed back .. interleaving was back on and on it has stayed. So the 24 hour thing that Lance talks about above was a bit ambitious.

First day of term today and my speed is down to 780 kbps.. oh dear. What a load of cr*p. This is so depressing.

Ted · Jan 20, 2009, 09:02:09

That was quite painless! (so far)
Checked this morning and the router is automagically showing "fast" and syncing at 8128 over7616.

Ping times to idnet.net have dropped from around 53 to 28, not bad for me.

Throughput seems about the same at the moment. Am i right in thinking that although my sync has gone up, my profile will have to catch up before any speed increase is apparent? If indeed there is one.

[attachment deleted by admin]

Rik · Jan 20, 2009, 10:13:40

You are, Ted.

Ted · Jan 20, 2009, 10:21:18

Quote from: Rik on Jan 20, 2009, 10:13:40
You are, Ted.

Thanks. Everything seems quite healthy at the moment and it does feel a little "snappier" (kiss of death)

I've been meaning to do it for ages just never got round to it.

Rik · Jan 20, 2009, 10:22:18

I've got a lot on that list.

Steve · Jan 20, 2009, 11:28:25

I think its time to try mine with interleave off as well. I have a full sync,22db downstream attenuation and low error counts. I am sure it went on when a 2wire was failing on my line.

Sebby · Jan 20, 2009, 19:02:21

It definitely sounds like you're line is capable of having interleaving switched off, Steve.

Steve · Jan 21, 2009, 07:45:29

Well its been removed, lets see if it stays that way. So far throughput seems ok for this time of day and ping times look excellent

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=15ms TTL=122
Reply from 212.58.224.138: bytes=32 time=15ms TTL=122
Reply from 212.58.224.138: bytes=32 time=15ms TTL=122
Reply from 212.58.224.138: bytes=32 time=16ms TTL=122

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 16ms, Average = 15ms

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 8128 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 7150 kbps
Actual IP throughput achieved during the test was - 6637 kbps

Rik · Jan 21, 2009, 09:46:38

That's about as good as it gets with ADSL, Steve, and you ought to do very well with ADSL2+.

Steve · Jan 21, 2009, 10:53:01

I am not expecting to see ADSL2+ before March 2010, its interesting that I've gained 20ms at least on ping times and throughput is just average or perhaps just slightly less for that time of day for me.

I wonder whether it will stay as fastpath as I my D/S margin has stuck at 15 since interleaving arrived a year ago which I think as I mentioned earlier was due to a combination of a failing router and a poor quality extension. If I recall a margin of 15db and interleave depth of 64 is the max BT can do to stabilize your line downstream.

It will be interesting to see if the margin does fall in 15 days back to 12 which it used to be at previously or interleave returns.

Rik · Jan 21, 2009, 10:57:41

If you're getting an 8128 sync, Steve, there's no reason for the margin to fall. In that situation, 15db is good.

Steve · Jan 21, 2009, 11:29:55

Ok, thanks Rik

Sebby · Jan 21, 2009, 19:47:16

Looking good, Steve.

vitriol · Jan 21, 2009, 21:30:35

nice pings steve

i just tried out of curiosity and got

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 24ms, Average = 22ms

nice

Steve · Jan 21, 2009, 21:38:19

I better get on the game.

Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=15ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 16ms, Average = 15ms

That's 20-30ms better for me on fastpath

g7pkf · Jan 21, 2009, 21:46:20

I think i should add to this thread before everyone thinks interleaving is a bad thing it is not.

let me explain.

interleaving should help on lines with problems. (except pendolino train problems-please do not ask as i am not a fan of them do a google for train adsl g7pkf and you will get the picture)

interleaving can actually speed up downloads as it effectively ensures that only part of the data needs to be re-transmitted if it gets corrupted in transfer as oppossed to the whole of the data packet. better explanation of this here curteousy of kitz

it can increase your sync rate as the line sees less "hard errors" see explanation above.

if you use the internet for downloading, browsing and email it matters not with interleaving on or off.

the only things that interleaving really causes a problem for are gamer's and VOIP (voice over ip). But even both these unless you are a real die hard gamer or you use voip as your main telephone then you may struggle to see (or hear) any differance.

hope that clarifies things a bit before you all go rushing to support and ask them to turn it off.

It should also be pointed out that whilst BTw state that applying interleaving shouldn't reduce your line speed, it does reduce the maximum line rate achievable from 8128kbps to 7616kbps due to the additional overhead required for check bytes. but if your getting sync rates like 7616 your living so close to the exchange chances of noise are considerably reduced so you "may" chose to get it turned off to get that last little drop outta the barell, so to speak.