Hey Guys,
I recently ran ICSI Netalyzr and I am receiving a report of high downlink buffering on my desktop. I ran the same test on a laptop and there was no buffering issue. I though this odd so I grabbed a network adapter for my desktop and ran the test again so I had the same connection method as the laptop, but no luck. I am still receiving high downlink buffering. Is there anything on my computer that could cause this buffering to occur only on one system? I do actually notice the issue while playing games like league. There are substantial frame drops that don't occur on the laptop and I would like to get this fixed.
Thanks in advance.
ICSI Netalyzr reports high downlink buffering on only 1 PC
Btw here is my TCP/IP Analyzer results:
« SpeedGuide.net TCP Analyzer Results »
Tested on: 2015.06.02 12:49
IP address: 174.54.xxx.xx
Client OS/browser: Windows 8.1 (Chrome 43.0.2357.81)
TCP options string: 020405b40103030801010402
MSS: 1460
MTU: 1500
TCP Window: 65536 (NOT multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 256
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 116
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
And speed test result on the closest server:
« SpeedGuide.net Speed Test Results »
10897 kbps down (~10.9 Mbps, 1330 KB/s)↓
3960 kbps up (~3.96 Mbps, 483 KB/s)↑
10240 KB downloaded in 7.698 seconds
3072 KB uploaded in 6.355 seconds
Tested on: 2015.06.02 12:57 EDT
Tested from: uplogon.com
Test Link: http://www.speedguide.net/speedtest/res ... st=4383187
Provider: pa.comcast.net
Location: Dallas, PA, US
« SpeedGuide.net TCP Analyzer Results »
Tested on: 2015.06.02 12:49
IP address: 174.54.xxx.xx
Client OS/browser: Windows 8.1 (Chrome 43.0.2357.81)
TCP options string: 020405b40103030801010402
MSS: 1460
MTU: 1500
TCP Window: 65536 (NOT multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 256
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 116
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
And speed test result on the closest server:
« SpeedGuide.net Speed Test Results »
10897 kbps down (~10.9 Mbps, 1330 KB/s)↓
3960 kbps up (~3.96 Mbps, 483 KB/s)↑
10240 KB downloaded in 7.698 seconds
3072 KB uploaded in 6.355 seconds
Tested on: 2015.06.02 12:57 EDT
Tested from: uplogon.com
Test Link: http://www.speedguide.net/speedtest/res ... st=4383187
Provider: pa.comcast.net
Location: Dallas, PA, US
Your buffering doesn't seem excessive, this is somewhat subjective as newer Windows versions auto-tune the TCP Window buffering depending on network conditions.
Generally speaking, that "buffering" is related to the size of the TCP Receive Window (RWIN). It needs to be large enough not to limit the speed of your connection, and small enough so that it will not introduce congestion on the network in general (the amount of data waiting to get to you, that may be discarded on congested routers).
In reality:
1. Congestion is a normal part of the TCP protocol, it tries to send data as fast as it can until it fills the buffers.
2. A buffer needs to be high enough to be called a buffer, i.e. by design it needs to allow for variations and increases in speed/latency.
3. Windows 7/8 auto-tunes the TCP Window, so you can only adjust how aggressive that auto-tuning algorithm is, you can't set it to a static number. Leaving it at "normal" works well for most broadband connections.
Because of all this, I wouldn't worry much about that Netalyzr result. If you still think there is a problem, please provide more specifics, i.e. how many milliseconds of buffering did it report.
I hope this helps. You may also want to look at this: http://www.speedguide.net/faq/what-is-t ... by-the-461
For gaming, you will want to balance between pure throughput and trying to minimize latency/jitter. You may want to check our Gaming Tweaks article here: http://www.speedguide.net/articles/gaming-tweaks-5812
Generally speaking, that "buffering" is related to the size of the TCP Receive Window (RWIN). It needs to be large enough not to limit the speed of your connection, and small enough so that it will not introduce congestion on the network in general (the amount of data waiting to get to you, that may be discarded on congested routers).
In reality:
1. Congestion is a normal part of the TCP protocol, it tries to send data as fast as it can until it fills the buffers.
2. A buffer needs to be high enough to be called a buffer, i.e. by design it needs to allow for variations and increases in speed/latency.
3. Windows 7/8 auto-tunes the TCP Window, so you can only adjust how aggressive that auto-tuning algorithm is, you can't set it to a static number. Leaving it at "normal" works well for most broadband connections.
Because of all this, I wouldn't worry much about that Netalyzr result. If you still think there is a problem, please provide more specifics, i.e. how many milliseconds of buffering did it report.
I hope this helps. You may also want to look at this: http://www.speedguide.net/faq/what-is-t ... by-the-461
For gaming, you will want to balance between pure throughput and trying to minimize latency/jitter. You may want to check our Gaming Tweaks article here: http://www.speedguide.net/articles/gaming-tweaks-5812
Disclaimer: Please use caution when opening messages, my grasp on reality may have shaken loose during transmission (going on rusty memory circuits), even though my tin foil hat is regularly audited for potential supply chain tampering. I also eat whatever crayons are put in front of me.
๑۩۞۩๑
๑۩۞۩๑