Good point to bring up. The underlying engine mechanism behind this is quite specific and it’s mostly about how your host controller services interrupts. Every time your mouse polls, the USB xHCI controller fires a hardware interrupt, which pushes a Deferred Procedure Call (DPC) onto your CPU’s queue. At 1000Hz that’s 1000 interrupts/sec, at 8000Hz it’s 8000/sec. Each one costs CPU cycles and, more importantly, can spike your DPC latency and push the OS scheduler around, which is exactly the jitter people complain about. On a 13900K the raw compute is nowhere near the ceiling, so the real bottleneck is firmware/OS interrupt handling and background processes eating that DPC queue, not the mouse itself. In practice the measured 0.38ms vs 0.92ms mouse-to-display figure is real, but whether YOU notice it is the question — 240Hz panels can only show ~4.16ms between frames anyway, so the sub-millisecond gains mostly show up in raw input smoothness and frame-to-frame consistency, not in a dramatic ‘it feels 2x faster’ way. My advice: enable 8K, but first close background apps, turn off any RGB/macro software, and use a latency tool like PCMark or the LDAT analyzer to watch DPC latency. If it stays stable and low, keep it. If you see spikes during intense firefights, drop back to 4000Hz which is usually the sweet spot for most people. Trust the measurements over the hype, but the hardware on your end can absolutely handle it.
"Display: Dell Alienware AW2725DF 360Hz QD-OLED"
"Mouse: Zowie EC2-CW + Vaxee PA"
"Pad: Artisan Zero Soft XL"
