Latency while downloading.

L

Lambchop

New Member
Joined
Dec 6, 2015
Messages
1
Reaction score
0
So this is a problem that all gamers in SA face. Too many games of counterstrike and dota are punctuated by "F*** I'm lagging" followed shortly by (off stage) "WHO THE HELL IS DOWNLOADING?".

All the research I have done suggests that it's only South Africans that get high ping/latency when someone is downloading, except people that suffer from bufferbloat. Does anyone NOT experience latency increases while downloading?

I am wanting to try my hand at streaming, I have streamed a few times and it's been awesome, but if I try stream and play CS:GO my usual ping of 70-80 which I am quite fond of gets ramped up to 160.

My question: Is this a function of my router or is this a function of South African DSL?

Details:
Router: Tp-Link TD-W8968
ISP: Axxess (2mb)

Proof:
I ran a nonstop ping to www.google.com (CMD ping www.google.com -t) and then conducted a speedtest on www.speedtest.net concurrently. The results were very obvious:

Resting latency is 33-35 downloading latency is 170-270 and uploading latency is 40-190
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\lambchop>ping www.google.com -t

Pinging www.google.com [41.160.35.143] with 32 bytes of da
Reply from 41.160.35.143: bytes=32 time=35ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=34ms TTL=54
Reply from 41.160.35.143: bytes=32 time=103ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=55ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=65ms TTL=53
Reply from 41.160.35.143: bytes=32 time=116ms TTL=53
Reply from 41.160.35.143: bytes=32 time=40ms TTL=53
Reply from 41.160.35.143: bytes=32 time=55ms TTL=53
Reply from 41.160.35.143: bytes=32 time=46ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=279ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=216ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=225ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=212ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=207ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=220ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=234ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=210ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=221ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=213ms TTL=54 |DOWNLOADING
Reply from 41.160.35.143: bytes=32 time=206ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=170ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=223ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=203ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=203ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=167ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=107ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=137ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=170ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=113ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=75ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=59ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=40ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=43ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=238ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=188ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=182ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=50ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=47ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=38ms TTL=54 |UPLOADING
Reply from 41.160.35.143: bytes=32 time=65ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=43ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=99ms TTL=54 |
Request timed out.
Reply from 41.160.35.143: bytes=32 time=143ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=244ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=133ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=61ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=66ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=41ms TTL=54
Reply from 41.160.35.143: bytes=32 time=247ms TTL=53
Reply from 41.160.35.143: bytes=32 time=43ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53

Ping statistics for 41.160.35.143:
Packets: Sent = 74, Received = 73, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 279ms, Average = 101ms

What I am looking for is any confirmation that it is only bufferbloat that causes this. I cannot install openWRT onto my router or DD-WRT because they both don't support the router I have, so any suggestions to fixing bufferbloat other than buying a new router would also be pretty shweet.

Thank you for reading this far you are a really cool person, also you should list reading forums as a hobby.
 
It's just ADSL line saturation as far as I know.

Other people from other countries are not in Africa, so they probably have fiber because it's affordable.
 
Lambchop said:
So this is a problem that all gamers in SA face. Too many games of counterstrike and dota are punctuated by "F*** I'm lagging" followed shortly by (off stage) "WHO THE HELL IS DOWNLOADING?".

All the research I have done suggests that it's only South Africans that get high ping/latency when someone is downloading, except people that suffer from bufferbloat. Does anyone NOT experience latency increases while downloading?

I am wanting to try my hand at streaming, I have streamed a few times and it's been awesome, but if I try stream and play CS:GO my usual ping of 70-80 which I am quite fond of gets ramped up to 160.
Click to expand...

Everyone lags if there isn't enough bandwidth to go around, it's not only a South African problem. You can not stream and play a FPS game with a 2MB ADSL connection, there simply isn't enough bandwidth. If you do manage then the quality of your stream will be pretty low which would defeat the point of streaming.

TP-Link modems are pretty good, especially the one you have, I highly doubt your modem is at fault.
 
Last edited:
The reason why it's a South African thing and the reason you suffer from it is your 2Mbps line being saturated.

I only use usenet to download, which doesn't upload like torrents do, and I just limit my download to 800KB/s on my 10Mbps line and my ping is the exact same with or without downloading, 30-40ms.

Do a test and download something and set a speed limit of 120KB/s and see what your latency looks like in game.
 
Latency is supposed to increase when you are uploading/downloading.

You are using up all of the available bandwidth when downloading so the latency will increase.
If you have a faster line then you will probably not notice the latency increase.

Or download a file and throttle the connection to a 1/4 of the speed and then check your latency.
 
As other mentioned it is the line saturation.

I have a Mikrotik which I configured with Queues to not allow one protocol to use more than 60% of my line. So the downloads leave 40% of my bandwidth free for other apps and latency is low.

Also important is when your upload bandwidth is saturated it will badly affect downloads even if downloads aren't saturated.
 
Lambchop said:
So this is a problem that all gamers in SA face. Too many games of counterstrike and dota are punctuated by "F*** I'm lagging" followed shortly by (off stage) "WHO THE HELL IS DOWNLOADING?".

All the research I have done suggests that it's only South Africans that get high ping/latency when someone is downloading, except people that suffer from bufferbloat. Does anyone NOT experience latency increases while downloading?

I am wanting to try my hand at streaming, I have streamed a few times and it's been awesome, but if I try stream and play CS:GO my usual ping of 70-80 which I am quite fond of gets ramped up to 160.

My question: Is this a function of my router or is this a function of South African DSL?

Details:
Router: Tp-Link TD-W8968
ISP: Axxess (2mb)

Proof:
I ran a nonstop ping to www.google.com (CMD ping www.google.com -t) and then conducted a speedtest on www.speedtest.net concurrently. The results were very obvious:

Resting latency is 33-35 downloading latency is 170-270 and uploading latency is 40-190
Ping statistics for 10.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\lambchop>ping www.google.com -t

Pinging www.google.com [41.160.35.143] with 32 bytes of da
Reply from 41.160.35.143: bytes=32 time=35ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=34ms TTL=54
Reply from 41.160.35.143: bytes=32 time=103ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=55ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=65ms TTL=53
Reply from 41.160.35.143: bytes=32 time=116ms TTL=53
Reply from 41.160.35.143: bytes=32 time=40ms TTL=53
Reply from 41.160.35.143: bytes=32 time=55ms TTL=53
Reply from 41.160.35.143: bytes=32 time=46ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=279ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=216ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=225ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=212ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=207ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=220ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=234ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=210ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=221ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=213ms TTL=54 |DOWNLOADING
Reply from 41.160.35.143: bytes=32 time=206ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=170ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=223ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=203ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=203ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=167ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=107ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=137ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=170ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=113ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=75ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=33ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53
Reply from 41.160.35.143: bytes=32 time=59ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=40ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=43ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=238ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=188ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=182ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=50ms TTL=53 |
Reply from 41.160.35.143: bytes=32 time=47ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=38ms TTL=54 |UPLOADING
Reply from 41.160.35.143: bytes=32 time=65ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=43ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=99ms TTL=54 |
Request timed out.
Reply from 41.160.35.143: bytes=32 time=143ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=244ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=133ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=61ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=66ms TTL=54 |
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=33ms TTL=54
Reply from 41.160.35.143: bytes=32 time=41ms TTL=54
Reply from 41.160.35.143: bytes=32 time=247ms TTL=53
Reply from 41.160.35.143: bytes=32 time=43ms TTL=53
Reply from 41.160.35.143: bytes=32 time=34ms TTL=53

Ping statistics for 41.160.35.143:
Packets: Sent = 74, Received = 73, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 279ms, Average = 101ms

What I am looking for is any confirmation that it is only bufferbloat that causes this. I cannot install openWRT onto my router or DD-WRT because they both don't support the router I have, so any suggestions to fixing bufferbloat other than buying a new router would also be pretty shweet.

Thank you for reading this far you are a really cool person, also you should list reading forums as a hobby.
Click to expand...

You're only on 2meg.thats why. Upgrade your line.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X