Are there any 20CN bqm's i can look at to confirm this?
I dont share my connection with anyone and its dedicated to 1 machine at a time so it just doesnt make sense to me how it can fluctuate so much. How can it be a stable 37-38ms at idle with the ping command only running (less than 100kbits up/down) but once i influence any traffic (500kbits+) it will fluctuate between 37-150ms.
I could understand it if i was close to maxing my bandwidth due to bufferbloat but at roughly 10% throughput and even up to 30-50% should it not be somewhat stable atleast within a few ms?
For example here is a quick ping command output while opening a simple web page it sends my latency spiking. Any amount of traffic seems to cause it to spike. As you can see its somewhat stable at idle but as soon as the web page is loaded its jumping up and back down. This just doesnt seem normal and with the highly varied latency i am finding it impossible to do anything that requires stable latency ie--gaming and voip.
Text |
1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
2627
2829
3031
3233
3435
3637
3839
4041
4243
4445
4647
| Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=41ms TTL=56Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56Reply from 80.249.99.130: bytes=32 time=37ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=37ms TTL=56Reply from 80.249.99.130: bytes=32 time=36ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56Reply from 80.249.99.130: bytes=32 time=45ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56Reply from 80.249.99.130: bytes=32 time=55ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56Reply from 80.249.99.130: bytes=32 time=41ms TTL=56
Reply from 80.249.99.130: bytes=32 time=42ms TTL=56Reply from 80.249.99.130: bytes=32 time=60ms TTL=56
Reply from 80.249.99.130: bytes=32 time=36ms TTL=56Reply from 80.249.99.130: bytes=32 time=41ms TTL=56
Reply from 80.249.99.130: bytes=32 time=38ms TTL=56Reply from 80.249.99.130: bytes=32 time=67ms TTL=56
Reply from 80.249.99.130: bytes=32 time=90ms TTL=56Reply from 80.249.99.130: bytes=32 time=42ms TTL=56
Reply from 80.249.99.130: bytes=32 time=41ms TTL=56Reply from 80.249.99.130: bytes=32 time=44ms TTL=56
Reply from 80.249.99.130: bytes=32 time=41ms TTL=56Reply from 80.249.99.130: bytes=32 time=60ms TTL=56
Reply from 80.249.99.130: bytes=32 time=40ms TTL=56Reply from 80.249.99.130: bytes=32 time=66ms TTL=56
Reply from 80.249.99.130: bytes=32 time=45ms TTL=56Reply from 80.249.99.130: bytes=32 time=40ms TTL=56
Reply from 80.249.99.130: bytes=32 time=44ms TTL=56Reply from 80.249.99.130: bytes=32 time=61ms TTL=56
Reply from 80.249.99.130: bytes=32 time=38ms TTL=56Reply from 80.249.99.130: bytes=32 time=83ms TTL=56
Reply from 80.249.99.130: bytes=32 time=48ms TTL=56Reply from 80.249.99.130: bytes=32 time=73ms TTL=56
Reply from 80.249.99.130: bytes=32 time=40ms TTL=56Reply from 80.249.99.130: bytes=32 time=40ms TTL=56
Reply from 80.249.99.130: bytes=32 time=74ms TTL=56Reply from 80.249.99.130: bytes=32 time=56ms TTL=56
Reply from 80.249.99.130: bytes=32 time=39ms TTL=56Reply from 80.249.99.130: bytes=32 time=117ms TTL=56
Reply from 80.249.99.130: bytes=32 time=115ms TTL=56Reply from 80.249.99.130: bytes=32 time=104ms TTL=56
Reply from 80.249.99.130: bytes=32 time=54ms TTL=56Reply from 80.249.99.130: bytes=32 time=75ms TTL=56 |
Could it not possibly be an issue with the line, perhaps a poorly configured or failing DSLAM, QoS or something related at the exchange? Would it be worth pursuing as a fault with the ISP?
In the event it shows anything of importance my live bqm graph is available here--
http://www.thinkbroadband.com/ping/share/80d502d9725... Note my idle periods are early morning 2am-8am.
Edited by drkdeath5000 (Wed 10-Aug-16 01:20:10)