Network adapter settings for gaming: what actually helps

26 October 2026 · ~6 min read

This is a different layer to our bufferbloat guide, which is about your router's queue - these are the real settings on the network adapter itself and in Windows, on Windows 10 and 11, that affect latency before a packet ever reaches your router.

This guide is one part of our full PC optimization checklist for gaming. To properly optimize a PC for gaming, you need to work through every real lever once: optimize background processes, optimize GPU driver settings, optimize CPU and device affinity, optimize RAM and storage, optimize your network, and optimize your display settings, each in the order that actually moves the needle on a real PC, not six separate half-remembered tips picked at random. Whichever topic brought you to this specific guide, the full PC optimization checklist is the fastest, most reliable way to optimize the rest of your PC too.

Energy Efficient Ethernet: a real, documented latency source

EEE powers down parts of the physical link during idle gaps to save power, then has to renegotiate speed on the way back up - a real, if usually small, latency spike at exactly the wrong moment on some adapters, well-documented as a competitive-gaming complaint on certain chipsets specifically. Disabling it in the adapter's advanced driver settings is low-risk and worth testing, since not every adapter is affected equally.

Interrupt Moderation / Interrupt Throttle Rate

Your network adapter batches incoming packet interrupts rather than firing one per packet, trading a small amount of added latency for lower CPU overhead - the correct default for most use, and a real lever to lower or disable for gaming on an adapter where it's exposed, at the cost of slightly higher CPU interrupt load. The same real tradeoff covered for a high-polling-rate mouse in our mouse settings guide.

Nagle's Algorithm and TCP_NODELAY

Nagle's algorithm batches small outgoing TCP packets to reduce overhead, a real source of added latency for an application sending frequent tiny TCP packets. The nuance most advice skips: most competitive multiplayer games send their actual gameplay traffic over UDP, which Nagle's algorithm doesn't touch at all - disabling it mainly matters for specific TCP-based applications, not gameplay latency in most modern titles.

Flow control and jumbo frames: not for internet gaming

Both are real settings with a genuine use case - local network file transfers and NAS traffic - and no meaningful benefit for ordinary internet gaming traffic, which never approaches the packet sizes or sustained throughput where either setting matters.

Driver version: newer isn't automatically better

A specific network driver release introducing a real latency or stability regression on a specific adapter is a documented, repeated pattern across several manufacturers, not a rare fluke. Worth checking release notes and real user reports before updating immediately, and worth rolling back to a known-good previous version if a new driver makes things measurably worse.

Frequently asked