|reply to DataRiker |
Re: DSL Latency Issues
Wow, it does say interleave. It used to be fast-path
ADSL Line State: Up
ADSL Startup Attempts: 4
ADSL Modulation: DMT
ADSL Data Path: Interleave
CO vendor: CTNW
Power Management State L0
Datapump Version: DSP 188.8.131.52, HAL 184.108.40.206
SNR Margin: 14.30 12.00 dB
Line Attenuation: 26.50 13.00 dB
Output Power: 0.00 8.59 dBm
Errored Seconds: 0 0
Loss of Signal: 0 0
Loss of Frame: 0 0
CRC Errors: 0 2
Data Rate: 8096 512
Interleaver Delay 4 1 (milliseconds)
Interleave Depth 32 4
INP 0.000 0.521
atucRevisionNum 1 ATU-C Vendor ID CTNW
TrainedPath Interleave TrainedMode G.DMT
Interlv delay 32 4
LowestTone 35 6
HighestTone 245 28
TonesExcited 210 23
NetRate 16192 512
AggrRate 16256 544
TotalRate 8128 736
LineRate 9588 800
ATTNDR 10720 896
ACTATP -1 -1
ACTPSD -364 -345
Estimated loop length: 5584 feet (bridge tap)
Framing Mode: 3 - (REDUCED OVERHEAD WITH MERGED SYNC)
TPS-TC Encoding ATM
ATM port status : Up
Rx data rate (bps) : 8096
Tx data rate (bps) : 512
actions · 2012-Nov-2 1:00 am · (locked)
I found out at least 3 customers are set to interleave now. And my parents are still on fastpath. It was set to interleave back in august when I called in for the previous issue. Again, we would only lose net access, but keep sync. Never had packet loss or sync instability. I'm on copper from me to the remote DSLAM and fiber was laid a few years ago from DSLAM to CO. As far as I know, the line is in good shape. No local hardware has been changed recently. I am on maxsync profile but it only connects at 8096 now. I really want to identify the problem and get back on fastpath. I haven't been responded to in the direct forum yet other than giving my # and basic info on the problem.
I now actually think the problem started a long time ago. I use my connection frequently for work and play. I probably stay on it the most in my area so I notice any blimp in service. I know how to identify when the problem is with me, at&t, or the server I'm connecting to. I understand the net can get congested at times. Over the last few years, very rarely I would lose net access but not sync. It would happen at any time of the day so I know it wasn't because someone was working on it. But it was so rarely that I ignored it. Sometimes it would come right back and others stay off for secs, mins, hours. Then a few months ago back in august it slowly started doing it more and more frequently over the course of a few weeks til I finally called in. Wouldn't this mean something has slowly degraded over time? They keep correcting it in software when it's mostly likely a piece of hardware going bad or something else. And what's up with the on-the-clock latency issues? It's 11am and my latency is fine. Is there peak hours when something is turned on? I'm going to try and let a ping run at 5pm and 6pm to see if it switches over.
actions · 2012-Nov-2 12:14 pm · (locked)
PashuneCaps stifle innovationPremiumReviews:
said by navigator:I wouldn't doubt that. Over time as more and more users are added to the network, AT&T may offer higher speeds, etc. and as a result if a certain part of the network isn't upgraded, it will begin to get saturated and things like latency, speed will be affected.
Wouldn't this mean something has slowly degraded over time? They keep correcting it in software when it's mostly likely a piece of hardware going bad or something else. And what's up with the on-the-clock latency issues? It's 11am and my latency is fine. Is there peak hours when something is turned on? I'm going to try and let a ping run at 5pm and 6pm to see if it switches over.
Interleave isn't causing this added latency however. Interleave is basically a hardware noise correction method (of some sort) that delays bits of data, analyzes them for noise, and corrects them if needed. If it were affecting your connection your second hop would be affected as well as the rest. At 15 ms you're probably on the 1st noise profile but you'd only lose 4-8 ms of latency max if you were switched back to fast path.
Typically the reason you're switched to interleave is noise or your line being unable to support full sync rates due to distance, line gauge, etc. I didn't like MaxSync for this reason back when I had DSL.
actions · 2012-Nov-2 9:27 pm · (locked)
Very informative reply, thanks.
Multiple people were switched to interleave when I first called in about the loss of net access. If there was a noise problem wouldn't we have lose sync too? The IP address would drop but the modem would stay synced up to the DSLAM.
So I tried figuring out these on-the-clock latency changes. I know it was good all day up til 3:30pm then I checked at 4:06pm and it had turned bad. It stayed bad til 12:15am. I was checking it on the dot at 12am and it was still bad. I let it go to about 12:08am before I stopped it. And then I tried again at 12:16am and now its back good. I noticed this happen at the exact same time last night, that's why I was checking it at 12. As of now the problem seems to exist from ~4pm-12:15am. Tomorrow I will try and let a ping run every 10secs or so around those times to identify the exact moment it happens. Any idea why it would be on time like this?
So what would be the optimal setup for me? I want low latency and stable connection even at the cost of some bandwidth. Can I have my sync data rate lowered so its more stable? Or have the sync profile changed?
Direct forum is switching me back to fastpath to see if that helps. Not sure when that will take place though. I may have to go back to interleave if the old problem comes back.
actions · 2012-Nov-3 2:33 am · (locked)