8000 Hz: A Closer Look

In general terms, polling rate can be described as the rate at which the data generated by the mouse is transmitted from the mouse to the PC via USB. Polling rate is measured in Hz; i.e., the number of times per second. The higher the polling rate—the lower the polling interval—the more frequently are the cursor position and any other input events (button inputs) updated, resulting in improved positional accuracy and generally reduced latency. At 1000 Hz, the polling interval is 1 ms, meaning the PC receives a new update every 1 ms. At 2000 Hz, the interval is 0.5 ms, at 4000 Hz, the interval is 0.250 ms, and at 8000 Hz, the interval is 0.125 ms.

8000 Hz: The Technology and How to Use It

In the past, multiple mice claimed to be capable of 2000 or even 3000 Hz polling have been released. However, each and every time, these claims turned out to be inaccurate. All of these mice had one thing in common: They were full-speed devices typically incapable of running at polling rates higher than 1000 Hz unless modified USB drivers are used. The Viper 8K, on the other hand, is a high-speed device and thus natively capable of polling rates higher than 1000 Hz. Furthermore, it is equipped with a sensor (Focus+) capable of running at a sufficiently high framerate, which ensures it's not just identical data being sent more frequently.

To set the Viper 8K to 8000 Hz, one does not need to do anything as the Viper 8K is set to 8000 Hz polling by default. If desired, it can be set to 125, 500, 1000, 2000, or 4000 Hz instead within Synapse. However, it is important to note that those values merely denote the maximum applicable polling rate. If the mouse isn't physically moved enough to generate a sufficient number of motion events (for 8000 Hz at least 8000 pixels worth of motion per second), less updates will be transmitted, resulting in a lower effective polling rate. Accordingly, it is strongly recommended to use a sufficiently high CPI step on the Viper 8K. I would advise using at least 1600 CPI, and possibly even higher steps depending on one's effective in-game sensitivity (turn circumference). The higher the turn circumference, the more physical motion is typically generated, and thus lower CPI is required to saturate the polling rate. Conversely, the lower the turn circumference, the less physical motion is generated, and thus higher CPI is required to saturate the polling rate. It should also be noted that on the Viper 8K, click and sensor motion data is detached internally. As such, click events will always be reported at the highest possible frequency irrespective of which polling rate the Viper 8K is set to otherwise. In short, even when not using the Viper 8K at 8000 Hz, the benefits of 8000 Hz polling still apply to the click latency.

In order to get the full benefit out of 8000 Hz polling, certain conditions need to be met. First, it is recommended to have a sufficiently powerful CPU; i.e., one with six physical cores and appropriately high IPC at the least. Second, the OS has to be capable of interrupt moderation of 125 μs or lower. This is true of Windows 8 or higher, where interrupt moderation on XHCI will typically be 50 μs, but not of Windows 7 and lower, where interrupt moderation is never below 1 ms unless changed manually, which isn't easily done. On EHCI, interrupt moderation can be expected to be 125 μs on Windows 8 or higher, which is sufficient but not optimal. Third, it is therefore recommended to plug the Viper 8K into a USB 3.x port in XHCI mode. Any USB 3.x ports forced into EHCI will behave similarly to a native USB 2.x port. As a general rule of thumb, one should be using a USB port native to the CPU and not connect any other high-polling devices to a port of the same hub. Even if all of these conditions are met, actual polling stability during higher workloads will further depend on general system and OS health. As such, it is recommended to use a reasonably optimized OS installation without any bloat in conjunction with the Viper 8K.

Performance Testing

I'll be testing general tracking, polling stability, and motion delay for 2000, 4000, and 8000 Hz each. All testing has been performed at 1600 CPI.

2000 Hz:

No surprises here. Count distribution is tight as MotionSync continues to be active at this polling rate. The Viper 8K is ahead of the G403 by roughly 0.5 ms, which is within expectations.

4000 Hz:

MotionSync ensures count distribution is as tight as ever. The Viper 8K is now ahead by almost 0.8 ms.

8000 Hz:

MotionSync is no longer active at 8000 Hz, which becomes plainly visible in the first plot (xCount). Compared to 2000 and 4000 Hz, I had to move the mouse significantly more to fully saturate the polling rate. The Viper 8K is almost 0.9 ms ahead of the G403.

8000 Hz (EHCI):

Lastly, for the sake of comparison, here are the results for running the Viper 8K at 8000 Hz in a USB 2.x port (EHCI). As you can see, general tracking suffers; 8000 Hz is never reached, and the motion delay advantage over the G403 ends up accordingly smaller.

Subjective Evaluation

Of course, the performance metrics obtained through empirical testing are just one side of the coin. The more pressing question is whether 8000 Hz is at all noticeable in games, and if so, to which degree.

To properly answer this question, note that someone being unable to notice something does not mean it isn't there objectively, or does not provide an objective advantage. The latter is most definitely true of 8000 Hz polling on the Viper 8K, so the matter shifts towards whether said advantage is meaningful and thus noticeable one way or another. That said, playing on a 165 Hz monitor at typically 200 FPS or more, I indeed struggled to notice a difference in terms of latency. As explained above, saturating the full 8000 Hz polling rate takes quite a bit of mouse movement, and thus isn't typically reached all the time anyway, so most of the time, the benefit in terms of latency compared to 1000 Hz is around 0.5 ms, which is well below the sensory capabilities of the average human. The greatest effect of 8000 Hz may indeed not be observed in terms of absolute latency, but rather general positional accuracy and smoother cursor feel, more specifically in games requiring high precision in regards to click timing. Particularly games supporting sub-frame input will benefit to a greater degree from 8000 Hz, such as Overwatch or Diabotical with their respective settings enabled. Generally, in order to get any use out of 8000 Hz, I'd recommend using a strong CPU and a 240 Hz or even 360 Hz display. Slower panels will inevitably struggle to even display the granularity afforded by 8000 Hz polling. Those with weaker CPUs may experience worse input response simply due to the higher CPU cost, which means any advantage gained by 8000 Hz immediately cancels itself out.

When choosing between 2000, 4000, and 8000 Hz, I would advise taking the middle route, which is 4000 Hz. At 4000 Hz, MotionSync is still enabled, which synchronizes SPI communication with USB polling events, and overall responsiveness is virtually on par with 8000 Hz while being lighter on the CPU. The parity in terms of latency is further underlined by the fact that 4000 Hz is much easier to saturate, so most of the time, there is no difference in practice whatsoever, not to mention that click events are polled at 8000 Hz anyway.

Appendix: List of Tested Games

As there is little reason to use the Razer Viper 8K at polling rates higher than 1000 Hz in non-competitive games, I'll exclusively list games that are typically considered competitive. In order to only use the Viper 8K at polling rates higher than 1000 Hz in games in which it makes sense to do so, and to use 1000 Hz or less in others, one can use Synapse's ability to assign different polling-rate values to specific application profiles that are automatically applied depending on which application is currently running. Please note that a game running fine for me won't necessarily run fine for everyone, as it merely means it generally works well with 8000 Hz polling. Conversely, a game not working well at 8000 Hz on a specific system isn't generally incompatible with 8000 Hz polling.

• Call of Duty: Black Ops II Up to 8000 Hz
• Call of Duty: Black Ops IIII Up to 8000 Hz
• Counter-Strike: Global Offensive Up to 8000 Hz
• Diabotical Up to 8000 Hz
• KovaaK 2.0 The Meta Up to 8000 Hz
• Quake Live Up to 8000 Hz