If you're running DD-WRT, read up on bufferbloat and QoS. Bufferbloat is where your network device prefers to wait until it receives enough data to blast full packets (no empty space) to maximize transmission. The cost is latency. QoS allows specific packet types higher priority in send order if multiple traffic arrives. Gaming is about shorter packets, which is opposite of tuning for faster file downloads.
You can't optimize for both. Some guides are for gamers, others for downloaders. The idea behind TCP Optimizer and other tools to keep multiple profiles to switch settings depending on what you're doing. If it's a dedicated gaming box, leave it static.
Many NIC drivers offer TCP/UDP offload support, having the NIC translate headers so CPU does less work. On a modern CPU, this overhead is very little unless you're hammered by traffic (like a web server). Also, cheap NICs don't really offload anything. I think this why Killer made so much money (better chipset).
For more advanced debugging, you need WireShark. The point is not to understand what's inside the traffic, but do you see dropped packets, retransmissions, etc? That's a clue your PC and the upstream device isn't aligned.
Bottom line: bang for the buck, choose a good router/switch (or install DD-WRT). Check MTU length. Turn on QoS.
Twitchy gaming traffic is not the same as improving long TCP sessions, so most advice doesn't apply to you.
Edit:
Bufferbloat Test by Waveform
You can't optimize for both. Some guides are for gamers, others for downloaders. The idea behind TCP Optimizer and other tools to keep multiple profiles to switch settings depending on what you're doing. If it's a dedicated gaming box, leave it static.
Many NIC drivers offer TCP/UDP offload support, having the NIC translate headers so CPU does less work. On a modern CPU, this overhead is very little unless you're hammered by traffic (like a web server). Also, cheap NICs don't really offload anything. I think this why Killer made so much money (better chipset).
For more advanced debugging, you need WireShark. The point is not to understand what's inside the traffic, but do you see dropped packets, retransmissions, etc? That's a clue your PC and the upstream device isn't aligned.
Bottom line: bang for the buck, choose a good router/switch (or install DD-WRT). Check MTU length. Turn on QoS.
Twitchy gaming traffic is not the same as improving long TCP sessions, so most advice doesn't apply to you.
Edit:
Bufferbloat Test by Waveform
Last edited: