High Polling Rates and CPU Load
A high mouse polling setting can change the amount of input activity a system handles. Its usefulness should be assessed in the actual application and computer rather than inferred from the label alone.
A practical approach
Begin with a known stable supported rate and record ordinary frame behavior. Test another supported setting in the same scene, keeping background tasks and sensitivity comparable. Note any repeatable stutter, responsiveness change or compatibility issue. If the result is inconsistent, restore the stable baseline and investigate the application and system rather than stacking unrelated tweaks.
Higher reporting rates should be evaluated with system behavior
Increasing input reporting frequency changes the stream of events the system must handle. Whether a higher supported rate is useful depends on the complete setup and application behavior, not only on the mouse specification. Smooth operation and reliable input remain important.
Compare a familiar task at two supported rates while keeping the rest of the configuration stable. Watch for repeatable changes in frame behavior or input consistency rather than a single fluctuating counter. Do not assume every hitch is caused by the rate; background activity and other software may matter. A documented lower-rate baseline is useful for troubleshooting, and selecting it temporarily is not a statement that the hardware's higher capability is meaningless.
Polling interval is not total input latency
Polling rate describes a reporting frequency. The corresponding ideal interval is 1,000 divided by the rate in hertz, expressed in milliseconds. For example, 500 Hz corresponds to 2 ms between reports and 1,000 Hz to 1 ms. Those intervals are not the complete delay from movement or click to a visible result.
The rest of the device, application, rendering and display path still contributes. Supported rates also depend on the exact mouse, receiver, firmware and connection. Record the actual configuration and compare stability as well as the nominal number. A higher advertised rate is a feature to evaluate in the whole setup, not a guarantee of a particular end-to-end latency or an automatic improvement in game results.
Frame time and mouse reports are different clocks
Display refresh, rendered frame rate and mouse reporting frequency describe different parts of a system. Their numerical values should not be treated as interchangeable. A monitor refreshing at 144 Hz has an ideal refresh interval of about 6.94 ms, while a mouse reporting at 1,000 Hz has a nominal report interval of 1 ms.
Those figures do not simply add into a universal latency prediction, because timing and processing throughout the system matter. When comparing setups, record both frame behavior and input settings. A high reporting rate cannot create frames the game does not render, and a fast display does not establish the quality of every mouse input. The useful approach is to understand each measurement's role rather than select a matching number by appearance.
An example to work through
For example, a demanding scene may behave differently from an empty practice area. A polling comparison that uses only the empty scene can miss the conditions in which the computer is normally used.
What to check
- Compare the same application workload.
- Record stability as well as subjective feel.
- Keep a known working rate available.
Sources and further guidance
NVIDIA: understanding system latency