By: zzyzx (zzyzx.delete@this.zzyzx.sh), May 25, 2022 3:02 pm
Room: Moderated Discussions
Jukka Larja (roskakori2006.delete@this.gmail.com) on May 25, 2022 6:01 am wrote:
>
> Is that linearly proportional to polling rate? So 16 ms for standard 125 Hz polling?
As I understand it, yes, but I may well be missing something in that piece. In particular, if everything works according to my current mental model, I have no idea how 8 kHz polling is supposed to succeed (I don't have anything faster than 1 kHz to test with).
> I do think people with 1000 Hz gaming mouse and a dual-core CPU are pretty small
> niche. That said, gaming mouse can be problematic in itself just because all
> the non-essential stuff that comes with it uses way too much CPU cycles.
I've been in that niche a few times, but I prioritize peripherals over CPU/GPU performance (and never regret it). It's usually feasible to do without the software.
I'm familiar with this problem because of a particular game that's heavily threaded and boosts itself to prio 13+ on most threads, so that it's tough to entirely get rid of the input loss even with a 6C12T CPU at 500 Hz polling. :(
>
> Is that linearly proportional to polling rate? So 16 ms for standard 125 Hz polling?
As I understand it, yes, but I may well be missing something in that piece. In particular, if everything works according to my current mental model, I have no idea how 8 kHz polling is supposed to succeed (I don't have anything faster than 1 kHz to test with).
> I do think people with 1000 Hz gaming mouse and a dual-core CPU are pretty small
> niche. That said, gaming mouse can be problematic in itself just because all
> the non-essential stuff that comes with it uses way too much CPU cycles.
I've been in that niche a few times, but I prioritize peripherals over CPU/GPU performance (and never regret it). It's usually feasible to do without the software.
I'm familiar with this problem because of a particular game that's heavily threaded and boosts itself to prio 13+ on most threads, so that it's tough to entirely get rid of the input loss even with a 6C12T CPU at 500 Hz polling. :(