OS X and high mouse usb pullingrates?!

[Frieg]

Hi,

I'm having quite a hard time finding a mouse for my MBP late 2011 with HS 10.13.6.

First I have tried the Logitech MX Anywhere 2s, knew beforehand that bluetooth won't work so I used it with the dongle. Didn't work either, skipping choppy and laggy cursor. Returned it, have given up with third party wireless solutions with my MBP

So I'm trying to use my Logitech G203 wired gaming Mouse now. And now I'm experiencing a new problem I have never heard of before (in windows):

I can set the mouse to usb pullingrates of 125, 250, 500 and 1000hz. The higher I go, the faster rise the cpu and gpu temperatures when I move the mouse. with 1000hz its so bad that I'm able to reach over 90 ℃ cpu and gpu temps by just waving around the cursor fast. only with 125hz I see no effect on the cpu/gpu temps.

what the actual foxtrott.uniform.charlie.kilo is going on here? how on earth can a fast moving mouse with high usb pullingrates cause the cpu/gpu get really hot?! is that another sh*tty implementation of OS X?

oh, and with 1000hz the USB ports buzz like hell...

 

[Frieg]

So, after the initial emotional rant, now stick to the facts:

everything above the standard 125hz seems to increasingly put stress to either the cpu and/gpu. as said, moving the mouse instantly causes the cpu & gpu temperatures to raise rapidly @1000hz and quite considerably @500hz. looking at the activity monitor, increasing the pulling rate causes the process WindowServer to spike in cpu usage up to 30%, just by moving the mouse!

has anyone experienced this with OS X before? I'm quite new in the Mac world and never experienced similar in the windows world. should 1000hz work perfectly or is the mouse handling that poorly implemented in os x that it can't handle higher pulling rates?

 

[BrianBaughn]

For the Logitech MX Anywhere 2S...were you using the latest software for it released on July 3?

Regarding the Logitech G203...since it's relying on the "Logitech Gaming Software" to do what you're doing you're probably better off asking Logitech but maybe someone here has delved into this before.

 

[Frieg]

I have tried the latest and three prior versions. googling this issue for hours didn't bring up any success story of solving this problem, only threads of unhappy customers who had this problem with Logitech and OS X for years with several mx mice. so I gave up and returned it while I was still able to.