Top QoS options for gaming: classic versus Cake versus per-device bandwidth caps.
Top QoS options for gaming: classic versus Cake versus per-device bandwidth caps.
Discussion also highlights that my usual QoS configurations lack options for most games, though they include notes about improving game performance. Regarding bandwidth restrictions, I’m worried that if two users hit their limits simultaneously, the overall network capacity could be exceeded unless I set very strict per-device caps. Adaptive QoS is an option but I’m hesitant—it would mean signing up for unclear spyware terms with trend micro lol.
Typically games don't require excessive bandwidth and are more affected by latency. Focusing on ACK, SYN, and possibly ICMP along with small packets can improve performance. If users hit bandwidth limits, a fair share should be allocated so both get half of the available network capacity. Prioritizing packages helps maintain smooth gameplay even under bandwidth constraints, which is what QoS aims for. For optimal results, examine the specific packets and ports a game uses to prioritize its traffic over downloads or media streaming—consider giving extra priority to real-time communications like voice chat or Skype calls.
Proceed to prioritize larger packets up to around 1KB. Regarding fairness, this applies regardless of QoS being enabled. It also uses a per-device bandwidth cap. When the limit is hit, devices using the most data are throttled until the issue resolves. That’s essentially how it functions.
Examine how your games perform in traffic so you can choose the right packages. If your router offers fine-tuning, it should depend on its QoS setup and flexibility. Aim for a fair-queueing method with choices between modes. The goal isn't to block heavy users but to ensure each device gets a balanced share. On typical home routers this is usually not possible.
~Note: Traffic you anticipate hitting bandwidth limits includes downloads, file sharing, and streaming (especially movies). With a fair queue, each device should receive roughly equal bandwidth. Prioritize game traffic for smooth play, and mark real-time streams as high priority. Streaming can be tricky due to its bandwidth needs, so keep buffers stable. Regular downloads are less critical as long as packets aren't starved.}
Gaming shouldn’t take less priority than VoIP. A 80ms delay in VoIP won’t be as noticeable as it would be during gameplay.
I believe both are similarly affected by delays and fluctuations (jitter). If every VoIP service experiences an 80 ms delay, it should work well. However, excessive jitter from network congestion becomes an issue. For optimal performance you’d aim for around 20 ms delay with minimal jitter. Up to 150 ms and 30 ms jitter are barely perceptible. In gaming, it depends on the game type; 100 ms is usually acceptable, but for competitive fast-paced games less is better. Ultimately it comes down to which factor matters most to you. It does matter, though only in a limited way. I manage three queues (real-time, priority, background) and can only exclude specific types like email. This isn’t comparable to the capabilities of a Cisco router or Linux-based system I previously used.
Determine the optimal maximum size for gaming performance. Consider 1KB as a starting point and evaluate the impact of lowering it. Assess whether lower settings might introduce jitter. Ultimately weigh the costs of overestimating versus underestimating the risk.