>> with full interleave and slow ADSL2
Out of curiosity are any of your lines stable enough to cope either without or with a lower level of interleave as I can't help but wonder how much the overhead cost is.
The benefit of not having FTTC is that the adsl2 DLM (both 21CN & TT) are a lot more flexible and not as harsh when it does see any errors.
Personally I prefer to let any occasional burst errors just get it over & done with, rather than have increased RS overheads and additional latency 24/7.
I notice the effects of interleaving far more than I do the occasional noise burst. Granted it depends upon individual lines but I'm sure Chrys is also of the same opinion for his line too.
Kitz I agree, and doing some speedtests that also measure latency seems to explain things.
My base latency to the bbc under aaisp is 8-9ms under fastpath, it was 17-18ms under interleaving.
During a tbb speedtest on sky latency was measured at 25ms, on aaisp under fast path 28ms (20-22ms during the downstream part of the test thanks to aaisp's qos systems), on aaisp under interleaving 60ms O_o
So the increase seems even more pronounced during TCP sessions. Things immediately were snappier when DLM switched me back.
The problem is also compounded on the modern internet where loading a single webpage can have a dozen or so dns lookups, each of these the primary metric is RTT for page loading time.
I have a weird ES spike of 3200, on my dslstats graph which is odd, those ES are not in the telnet data, the spike is when I powered up modem after firmware swap. I think on this new dsl firmware this might be a problem when powering down modems if this gets passed up to the dslam. But I think its only since link time that gets passed on. I also think this might be a dslstats glitch, powering down a modem shouldnt cause 1000s of ES thats a duration of 50 minutes of continuous errors. I left the modem down for 3 15 min cycles so close to 50 mins, but it was powered off when plugging the dsl cable back in, so that 45mins downtime is not in the memory of it. Very odd.
Since Link time = 13 hours 25 min 1 sec
FEC: 0 131
CRC: 126 13
ES: 93 13
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0