Mouse Stutter During High System Load

28 May 2023

Mouse stutter that appears during a demanding task should be investigated with the workload in view. The visible symptom may involve the application or system rather than the sensor alone.

A practical approach

Compare a familiar light task with the demanding scene while keeping the device settings fixed. Record what else is running and whether the entire display response becomes uneven. Test one supported polling setting change only after establishing the baseline. Avoid installing untrusted optimization utilities or disabling protections in pursuit of an unexplained performance claim.

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.

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.

A recorded baseline makes troubleshooting reversible

Before changing settings, record the mouse model, connection, DPI, reporting rate, active profile and relevant application options. Add the surface and any recently changed hardware. This creates a known state to return to when an experiment does not help.

Keep the baseline simple and use supported settings rather than a collection of unexplained tweaks. Change one variable at a time and note the result in the same task. If a change is not useful, restore the previous state before trying another. This prevents several small adjustments from accumulating into a configuration nobody understands. A short, clear record is more valuable than dozens of screenshots with no indication of which settings were active when the symptom appeared.

An example to work through

For example, a mouse that appears smooth on the desktop but uneven during a specific heavy scene may be exposing a workload-related issue. Repeating the same scene helps make that pattern visible.

What to check

Record the workload where stutter appears.
Observe the whole display response.
Use reversible supported changes only.

Sources and further guidance

NVIDIA: understanding system latency