What polling rate actually means
Polling rate is how many times per second the mouse reports its position to the computer. At 125 Hz that happens every 8 milliseconds; at 1000 Hz, every millisecond. It is how often the system learns where the cursor is.
The gain is largest at the bottom of the scale. Going from 125 to 500 Hz cuts the delay from 8 ms to 2 ms, which is noticeable in fast movement. From 500 to 1000 Hz the cut is a single millisecond — measurable, rarely perceptible. That is why the marketing jumps to 4000 or 8000 Hz deliver so little: the curve has already flattened.
The CPU cost
Every report from the mouse raises an interrupt the processor has to service. At 1000 Hz that is a thousand interrupts per second; at 8000 Hz, eight thousand. On modern machines the impact is small, but it is real, and it shows up exactly when the CPU is already saturated — which is competitive gaming, the same scenario where the high rate was supposed to help.
On older computers or entry level processors, very high rates can reduce average FPS. If you landed here investigating a performance drop, test at 500 Hz and compare: the result is often steadier than at 1000.
How to change it, and why readings diverge
The rate is set in vendor software — Razer Synapse, Logitech G HUB, Corsair iCUE, SteelSeries GG — usually under a performance section. Some mice offer a physical button or key combination to switch without software.
If the value measured here sits well below what you configured, the cable, the distance to a wireless receiver, or USB 3.0 interference are the usual suspects — 3.0 ports are a classic source of noise for 2.4 GHz receivers. Before concluding anything, repeat the measurement with wide, continuous strokes: a small sample skews the result.
It helps to know how the measurement works. Browsers do not deliver one event per mouse report: they group the reports and deliver them in batches, so counting events would always land near 60 per second, whatever mouse you own. This test uses `getCoalescedEvents`, which returns the raw samples inside each batch — that is how 500 or 1000 Hz becomes visible. It works on Chromium based browsers: Chrome, Edge and Opera. Firefox and its forks implement the method but do not expose the samples in between, and delivery stays pinned around 60 Hz — including on 144 Hz monitors, because the limit belongs to the browser rather than the screen. When it detects that pattern, the test says so rather than presenting the browser ceiling as if it were the mouse rate.
Frequently asked questions
- Why does the reading not match my configured 1000 Hz?
- Short or intermittent movement drags the average down, so keep moving in wide strokes for a few seconds. If the number stays low, check the cable, how far the wireless receiver sits, and whether it is plugged into a USB 3.0 port. And check which browser you are in: on Firefox and its forks the reading stays around 60 Hz whatever the monitor, and the test flags it when that happens.
- Is 1000 Hz worth using?
- Worth it if your CPU has headroom. The real gain is leaving 125 Hz behind; from 500 to 1000 the difference is one millisecond. On weaker machines, 500 Hz often produces a steadier result.
- Does a high rate drain a wireless mouse faster?
- Considerably. Reporting a thousand times per second costs far more than 125, and battery life commonly halves or worse between the two extremes.
- Do wireless mice poll slower than wired ones?
- Not necessarily any more — dedicated receivers hold 1000 Hz reliably. Bluetooth is a different story: it usually sits at 125 Hz and suffers more interference.