Those with fancy gaming mice...

  • Thread starter Thread starter V F
  • Start date Start date

V F

V F

Soldato
Joined
13 Aug 2003
Posts
21,184
Location
UK
With them set to 1000Hz do you get 0 CPU usage?

Had been reading some old posts from 2014...

reddy89 said:
Well, with today's processors it's negligible. My CPU doesn't budge from 0% when moving the mouse around on the desktop @ 1000Hz.

metal571 said:
Seconding this...you have to be joking if you really think with modern processors that 1000 Hz actually causes any kind of appreciable CPU hit


With the Razer Copperhead on an i7 3770k I see the processor usage jump from 2 - 7 percent, whether it is 125, 500 or 1000Hz.
 
Zowie FK series at 1000Hz not seen any CPU usage from moving the mouse - last time I did I think was on my Pentium 4. You might find some vendor specific drivers/software or USB 3 drivers aren't so happy or something.
 
Or the Copperhead is so old? 2005/06 if I remember correctly. It is connected to the Intel USB 3 ports.

Even the Logitech MX1000 triggers processor usage.
 
Try another USB controller. If you are using USB2 on the motherboard, try USB3 etc. Some controllers simply can't handle the speed.

https://www.youtube.com/watch?v=iV8g8lm1kIU

My motherboard has the following:
Intel USB2
Intel USB3.1
ASMedia USB3.1

The Intel USB2 ports have significant DPC latency. The other 2 controllers give me a stable 12us when moving the mouse (from an idle base of 4us).
 
It does the same with any port. It has always been on the native Intel USB3 ports. However, quick swipes its 0 - 1% but if you constantly move it erratically fast it spikes.

I'll try that above this evening, sadbuttrue.
 
So that person I quoted must have only been doing swipes and stating it is 0% which is true like I found between 0 - 1 - 2% usage. They weren't very thorough though.

Thought it was interesting viewing this. His seems a little worse?

 
Moving the mouse inside any window will generate cpu usage - everything your mouse moves over is being updated in some way. Naturally a higher polling rate will lead to more cpu usage due to increased updates to the area your mouse is moving over.

Testing should be done over an empty desktop where you'll not see any significant change.
 
Moving the mouse inside any window will generate cpu usage - everything your mouse moves over is being updated in some way. Naturally a higher polling rate will lead to more cpu usage due to increased updates to the area your mouse is moving over.

Testing should be done over an empty desktop where you'll not see any significant change.
Tried this, over chrome about 15%, spotify 20%, desktop was just idle. Just set it to 1000Hz and forget.
 
I get 10-11% CPU use moving the mouse around over the Spotify window with 125-500Hz and I think the peak increased to 13% with 1000Hz nothing else really shows any noticeable change in CPU use over 125Hz for me.

I have some tweaks to core parking and Windows performance profile that might be making a difference dunno.
 
How do people manage to use these mice for 2000dpi and higher? I find them way too sensitive and tweaking for a few hours I seem to like 500Hz and 1600dpi. Everything else feels too twitchy. As if the Razer is picking up my hand slightly shaking when using scopes. Or it is the nylon desk mat or both.

Quick turns with this feels so nice with Crysis 2. Shame Quake Champions isn't up and running to test it.
 
Not a fan of super high DPI personally - I usually use 400-450 personally with Windows setup for 1:1 mapping and MarkC's mouse fix.

500Hz can often provide a more stable input in my experience but 1-2 sensors like the 3360 seems to benefit from 1000Hz - while the 3310 definitely has some erraticism which is less well masked at 1000Hz v 500Hz IMO.
 
Oh wow, moving the mouse whacks up my CPU usage! I have never noticed that before, so thanks for that snippet OP. :p

I have my mouse at 6000dpi but the windows pointer speed at the default of just under half way. I think it is more accurate like that? But is it having a detrimental effect on my CPU usage in games etc? Should I have say, 600dpi and the windows pointer speed maxxed out?

It bumps up my CPU usage by about 10%. (2700K @ 4.7GHz)
 
I have my mouse at 6000dpi but the windows pointer speed at the default of just under half way. I think it is more accurate like that? But is it having a detrimental effect on my CPU usage in games etc? Should I have say, 600dpi and the windows pointer speed maxxed out?

It bumps up my CPU usage by about 10%. (2700K @ 4.7GHz)

I think it depends on the game how much the fps matter to you or if the game is extremely demanding on the CPU. I personally didn't notice any fps hit with 1000Hz but I really felt it too sensitive/twitchy.

I assume you have the Windows mouse settings to to 6/11?

Mark Cranness said:
- Exact 1-to-1 only works when the mouse pointer speed slider is in the middle, 6/11 position. If you use slider positions to the left of middle, you will always get green bars.

http://donewmouseaccel.blogspot.co.uk/2010/03/markc-windows-7-mouse-acceleration-fix.html
 
Zowie has their own online Hz checker. Which shows as Roff mentioned 1000hz on my fk can fluctuate down to 880hz. At 500hz it's much more stable. So I just use that.
 
Moving the mouse very actively over a Chrome window bumps one core on my CPU to about 15% while the rest stay the same so it's certainly not a level of usage I'd worry about personally.
 
How do people manage to use these mice for 2000dpi and higher?
Mousing on a 27" 1440p screen, I have mine set to 3800dpi.
I Claw the mouse and moving it about 1½" is enough to get the pointer the full width of the screen. I control my mouse with very slight finger movements.
Others I know have much lower dpi and favour massive great desk-sweeping motions to move their mouse around.

Horses for courses.
I can't see the 16,000dpi of some gaming mice being of use, though...!!
 
Zowie has their own online Hz checker. Which shows as Roff mentioned 1000hz on my fk can fluctuate down to 880hz. At 500hz it's much more stable. So I just use that.

AFAIK no setup will hit 1000Hz constantly like it does 500Hz - but I've found with the newer Avago 3310 sensor used in Zowies and some other mice don't seem to like fluctuating update rates - you get some weird erraticism in the input that isn't there with a constant 500Hz and not seen on some other sensors at 1000Hz. Its actually slightly there still at 500Hz but occurs significantly less often.

Easiest way to see it is to draw a circle over and over very quickly with the mouse pointer - if you are fairly consistent at 500Hz it should stay in roughly the same place while at 1000Hz the position of the circle will start to drift away a little no matter how much you try to keep it in the same place.

Personally I prefer the Avago 3090 (which sadly seems to be being phased out) - while it doesn't have quite the micro sensitivity of the 3366/3360 (which seem to benefit from 1000Hz nicely probably due to the high sensor resolution/update rate) IMO it has the best linear response of any sensor I've tried - absolutely no indication of any masking of input errors or other smoothing etc. absolutely no positive or negative acceleration, never the slightest hint of prediction snapping.
 
Back
Top Bottom