Debunking Gaming Latency Myths on Ryzen 7800X3D/9800X3D, Windows 11,RTX4090/5090

[witega]

I agree with "some" of the things. Like HPET for windows 11, it's used as a reference with your main timer to counter desync. And I think that's the only thing you're correct on. Windows 11 scheduler is bad. That's why the registry tweaks for "Win32PriorityFull" & "Game" profile are very advantageous. I think these 2 tweaks alone have the greatest impact on input latency and frame times. "Win32PriorityFull" specifically you have to find the right setting that works for your preferred use case, balancing between multitasking or pure input latency. I multitask while I game so 26decimal or 41decimal as been really good for me and preserves input latency.

The fact that you have to enable "Game Mode" is evidence enough that the Windows 11 scheduler is bad just for the dual ccd X3D chips to perform. They literally had to hack a work around to get it to work.

8000hz polling mouse is overkill, you're overloading your cpu with that many interrupts for no gains. Lowest your system can schedule for is 0.5ms on windows 11. Games only ask for 1ms. 1000hz is 1ms. 2000hz is 0.5ms. Anything above that is pointless and only ADDING latency by flooding the queue. So 2000hz is ideal even if games only ask for 1ms because it has 2 opportunities to get processed in time if it misses the first chance.

Spread spectrum introduces jitter because it's constantly adjusting your clock speeds causing desync. It's about what is more of a problem. I prefer stable clock speeds, Spread spectrum on negatively affects your ram speeds and drive speeds as well. Pretty much overall system speed. Just test it with it on and off. I've done it. It had a huge impact on my NVME IOPS. I doubt the possible EMI caused by it is more impactful than the jitter, and other negative system impacts.

Plugging in things to ports from CPU vs CHIPSET, mmm totally wrong about that one. That's why your graphics card "MUST" be on the slot closest to your CPU.

Tweaking your system is a requirement if you want good input latency. Out of the box, windows 11 is bloated with a lot of things adding I/O overhead. Just onedrive enabled really thrashes your systems I/O, you can check it with process monitor. And that's just 1 thing. A lot of the tweaks out there do work. But they work specifically for your version of windows and hardware setup. For example, the BCDEDIT stuff doesn't work on windows 11 for my hardware in a positive way. But they do work on windows 10. Not only that, there are a handful of tweaks that are generally advantageous for everyone and there are some that are not. Then there are some that are overkill like assigning affinities, that do work but not worth the hassle vs gains. But again everyone's situation and preferences are different.

One of the MODs really needs to create a wiki for definitive answers to these things so people aren't constantly going around spewing bad information.

A lot of what you wrote is exactly the kind of “tweak folklore” this thread is trying to separate from reproducible mechanisms.

A general principle up front: if a tweak has a large impact, it should show up consistently in frametime plots, queue depth behavior or input-to-photon measurement. Not just subjective feel.

Right now many of these claims are asserted with certainty but without a causal chain or controlled measurement.

“Windows 11 scheduler is bad, Win32PriorityFull/Game profile registry tweaks are huge”

This is a strong claim but it needs strong evidence.

Windows scheduling is not governed by a single registry magic value.

Priority tweaks often just reshuffle contention, they don’t remove it.

They can also increase jitter by starving background driver work (which is exactly how you get DPC spikes and missed HID events).

If these tweaks were “greatest impact on input latency,” they would be documented by Microsoft/NVIDIA/AMD, measurable across systems, standard in competitive setups, etc.

Instead they’re highly anecdotal and version fragile.

Extraordinary claims require controlled data not “works for me”.

“Game Mode proves the scheduler is bad, it’s a hack”

Game Mode is not an admission of failure. It’s simply a policy toggle. It reduces background update activity, prioritizes the foreground game process, adjusts power/QoS behavior.

That’s not a “hack”, it’s an explicit user facing workload mode like “Low Latency Mode” in drivers.

Also dual-CCD issues are largely irrelevant to 7800X3D/9800X3D, which are single-CCD parts.

“8 kHz floods the CPU, anything above 2 kHz adds latency”

This is overstated and partly incorrect.

Interrupt cost from 8 kHz HID is tiny on modern CPUs.

Windows timer resolution is not the same as input sampling ceiling.

Games don’t “ask for 1 ms”, they poll/input-sample per frame and via raw input paths.

The correct statement is above 1–2 kHz yields diminishing returns for most engines, but it does not automatically “add latency” unless something else is broken (driver/DPC contention).

So yes diminishing returns but no in that it does universal harm.

“Spread Spectrum introduces jitter and hurts RAM/NVMe IOPS hugely”

Spread Spectrum modulates the reference clock slightly to reduce EMI. On modern systems the modulation is extremely small. PCIe/NVMe have their own clock recovery mechanisms and large IOPS changes are far more likely from power management, thermals, firmware or background I/O.

If you have benchmark data, post it with controls. Otherwise this is exactly the kind of claim that turns into superstition.

“CPU vs chipset USB is totally wrong because GPU must be closest slot”

This is a category error.

GPU primary slot proximity is about PCIe lane routing and signal integrity. USB topology is about host controllers, chipset fabric hops and interrupt routing. They are not the same mechanism.

CPU-attached USB can be marginally cleaner in edge cases but it’s not a magic requirement. That’s the nuanced position.

“Tweaking is required, Windows is bloated, OneDrive thrashes I/O”

Background tasks can matter, sure but “debloat everything” is not a latency strategy, it’s often instability by another name.

Most “tweaks” people stack are undocumented, non-portable and frequently placebo. The highest impact wins are stable BIOS, sane drivers, controlled queue depth, avoiding GPU saturation, minimizing overlays.

OneDrive isn’t secretly adding 20 ms of input lag unless your system is already misconfigured.

"One of the mods should create a wiki

I actually agree with your last point that Blur Busters would benefit from a measured, versioned wiki separating real queue/frametime mechanisms from legacy tweaks and myths.

That’s basically the goal of this thread.

In conclusion, I’m not claiming “nothing matters” I’m claiming the tweaks that matter are the ones with a clear mechanism and repeatable measurement, not registry roulette and absolute statements like “MUST” or “huge impact” without data.

If you have CapFrameX plots, LDAT measurements or controlled before/after results for Win32PriorityFull or Spread Spectrum on modern Win11 + X3D, I’m genuinely open to looking at them. That’s the level this discussion needs.

[Hyote]

they would be documented by Microsoft/NVIDIA/AMD, measurable across systems, standard in competitive setups

Need to comment on this. Some here try to deny the existence of "tweaking" with all the serious sounding methodologies that are just as flawed as anything else. Tweaking is a very real thing and whoever goes down that path will probably not come back to just using their system as is. The amount of changes you can make in a positive direction outweighs absolutely everything. Companies make their products in specific ways and oftentime overlooked things enough to create something that can become a niche, just like this is. I wonder when people will stop using the topic of competitive setups as an example because they do not do anything special. They are standard computers with standard installs. And they are set up for ideal performance with minimal settings, that is it. I won't repeat myself here about why they don't need super secret NDA tweaks on their computers but that's about it.
I see many known people in these communities making it their life's mission to spread the word about how it's all hardware and how everything just has to be set up properly and suddenly tweaks are bad, Windows is already preconfigured ideally so it's all in people's heads.
So yeah, glory to the tweakers.

[yehaw]

Just saw your thread after replying to an almost similar thread. Though there are tweaks you can make to improving latency, I found a lot of it useless and bad as this thread covers some of them. I did some testing, you can read here my conclusion if you're interested (dpc latency/power draw/cstates/speedshift/speedstep):

viewtopic.php?t=11394&start=40#p122227

I didn't review entire thread, glossed over some things:

OneDrive isn’t secretly adding 20 ms of input lag unless your system is already misconfigured.

This is wrong the wrong way to look at it. Debloating is to reduce interrupts and executions the CPU has to deal with to maintain the smoothest experience possible at all times. The less interupts/executions that hit your CPU, the more consistent your smooth experience remains. That's why Latencymon is the most popular tool in the tweaking community. You also don't debloat to gain a 20ms advantage, that comes from your hardware (monitor/mouse/keyboard/fps). You debloat to remove the large variance of instability to your experience that the default Windows provides.

The default Windows experience is an absolute mess, there's no point in defending it. Maybe it's a better experience on top of the line hardware that can brute force through it, but I've done extensive testing stock vs my personal stripped 25h2. My system which is an old budget 12th gen (12400f/4060) is an absolute mess on stock W11 25h2. Random hitching, slow loading explorer at times, animations are laggy, games run decent but you see the hitches at times, etc. Sometimes it feels decent, sometimes it feels like shit. It's never a wow experience. It's an inconsistent mess.

Tweaked and stripped OS. No random slowdowns, animations look incredibly smooth at 240hz, like they should. Explorer opens instantly. Flyouts snap out instantly. It's just a far more smooth and consistent experience across the board, including games. Why is that? You reduce all the background noise that is constantly pinging your CPU. Even if a windows process is idle in the background using only 30mb, it still has the ability to send short workloads to your CPU. When you pair this with the mass amount of bloat that comes pre-installed Windows, you can have upwards of 30+ services/process/tasks sending random pings to your CPU. Defender, Edge, SmartScreen, Update, etc, etc. It's a mess.

It's very easy to test this theory without debloating. Just switch to a Linux distro and you can see the ultra-responsive experience even a budget PC can deliver. Silky smooth animations, instantly opening apps, file browser, etc. If you decide to test, make sure you install and don't just run it off your thumb-drive to see . I recommend endeavouros if you want to try it out. You can achieve the same experience on Windows, it just requires a lot of work.

My dream, Microsoft would move the Pro version to a modular system integrated with an offline catalog. It gives you the basics to get online, then you load the catalog and and pick modules you need. Don't need updates? Don't install the module. Need printing? Install the module,. Essentially let you build the perfect and most lean Windows experience possible. Leave the bloated mess to Home version. Pro has been neutered to hell, they don't even respect group policy settings for a lot of things you change and even have secret medic services that re-enable things you want disabled. It's garbage out of the box.

Stripped OS can also bring a lot of problems if you don't know what you're doing or just using someone else's premade setup. I think this is why so many people dismiss tweaking/debloating the os. It's so easy to break an entire system with just 1 removal or 1 tweak or using pre-made configs that will never work perfectly across an entire range of different hardware/drivers. Removing components is just part of the process, those components often leave traces in other areas despite the main component being removed which will lead to worse issues. It's highly intricate work to perfectly debloat an OS. Read, research and make your own setup tailored to your hardware if you want the perfect desktop/gaming experience and stop relying on the work of others.

[witega]

they would be documented by Microsoft/NVIDIA/AMD, measurable across systems, standard in competitive setups

Need to comment on this. Some here try to deny the existence of "tweaking" with all the serious sounding methodologies that are just as flawed as anything else. Tweaking is a very real thing and whoever goes down that path will probably not come back to just using their system as is. The amount of changes you can make in a positive direction outweighs absolutely everything. Companies make their products in specific ways and oftentime overlooked things enough to create something that can become a niche, just like this is. I wonder when people will stop using the topic of competitive setups as an example because they do not do anything special. They are standard computers with standard installs. And they are set up for ideal performance with minimal settings, that is it. I won't repeat myself here about why they don't need super secret NDA tweaks on their computers but that's about it.
I see many known people in these communities making it their life's mission to spread the word about how it's all hardware and how everything just has to be set up properly and suddenly tweaks are bad, Windows is already preconfigured ideally so it's all in people's heads.
So yeah, glory to the tweakers.

Well I'm using “tweaking” in a narrower engineering sense, which is different than how you are using it in a very expansive way.

No one is denying that configuration choices matter. Obviously they do. Drivers matter, power settings matter, avoiding GPU saturation matters, disabling problematic background hooks matters. None of that is controversial.

What I’m disagreeing on is the leap from: "some settings matter" to "the amount of changes you can make outweighs absolutely everything" and "whoever tweaks will never go back". None of this is a technical claim.

If a tweak produces a real latency or frametime improvement then it should be explainable by a mechanism (queue depth, scheduling, buffering), measurable in frametime variance or input-to-photon tests and repeatable across similar systems. Otherwise, we’re just doing post-hoc reasoning, placebo reinforcement and endless version specific superstition.

Competitive setups are relevant precisely because they are boring yes. You said it yourself: pro setups are mostly standard installs with minimal extras. That’s the point. If registry micro surgery and undocumented scheduler hacks were truly "the greatest impact" then high level competitive environments would converge on them quickly because money is on the line and instability is unacceptable. Instead the convergence is toward stable defaults, Reflex/anti-queue features, clean driver stacks, consistent frame pacing, etc. not registry roulette.

I’m not interested in policing what people enjoy doing to their PCs. If tweaking is a hobby, fine. But this thread is about debunking myths, not denying that settings exist.

So the standard remains simple: Show mechanisms. Show measurements. Avoid universals. That’s all.

[naporitan]

.

[soul4kills]

“8 kHz floods the CPU, anything above 2 kHz adds latency”

This is overstated and partly incorrect.

Interrupt cost from 8 kHz HID is tiny on modern CPUs.

Windows timer resolution is not the same as input sampling ceiling.

Games don’t “ask for 1 ms”, they poll/input-sample per frame and via raw input paths.

The correct statement is above 1–2 kHz yields diminishing returns for most engines, but it does not automatically “add latency” unless something else is broken (driver/DPC contention).

So yes diminishing returns but no in that it does universal harm.

You don't understand how it works. Interrupts are called interrupts because it interrupts the CPU and stops everything else to see what the device wants. For example, it interrupts the game loop. At 8000hz, that's a lot. FYI frame gen and game loops run at independent frequencies of each other.

Input latency is an accumulative problem that has a large range of possible causes. Your debunk of just do nothing is nonsense.

Edit: Also nothing in my reply is "folklore". Spread spectrum is not folklore, we all know what it does. Win32prioritySeperation is not folklore. Its well documented how it can affect your machines latency and performance. It's advance windows settings hidden from the normal user. Connection to cpu vs chipset is not folklore, it's fact that cpu connection is more direct and faster than the southbridge. Southbridge's purpose is to handle slower things so cpu can focus on the faster stuff. Why do the manufacturers even have a set of ports direct to the cpu and a set to the southbridge? There must be a reason....

[yehaw]

In order: Current, Min, Max, Average

Top, De-bloated W11 25H2
Bottom, Stock W11 25H2
Both same drivers, both with latest updates applied

So for those that saying de-bloating has no affect, there's your proof you're wrong. And this is measured in MS not US like latencymon.

Might your PC act different or have better results? Yes, but for those on CPU with limited core count, you will feel a drastic difference. For those on more modern CPU that have lots of cores, these CPUS can spread the interrupts/executions workloads better due to higher core count, but debloating is still worth it on any system, imo.

[urikawa]

What debloat do you use ?

[Maelstrom]

“8 kHz floods the CPU, anything above 2 kHz adds latency”

This is overstated and partly incorrect.

Interrupt cost from 8 kHz HID is tiny on modern CPUs.

Windows timer resolution is not the same as input sampling ceiling.

Games don’t “ask for 1 ms”, they poll/input-sample per frame and via raw input paths.

The correct statement is above 1–2 kHz yields diminishing returns for most engines, but it does not automatically “add latency” unless something else is broken (driver/DPC contention).

So yes diminishing returns but no in that it does universal harm.

You don't understand how it works. Interrupts are called interrupts because it interrupts the CPU and stops everything else to see what the device wants. For example, it interrupts the game loop. At 8000hz, that's a lot. FYI frame gen and game loops run at independent frequencies of each other.

Input latency is an accumulative problem that has a large range of possible causes. Your debunk of just do nothing is nonsense.

Edit: Also nothing in my reply is "folklore". Spread spectrum is not folklore, we all know what it does. Win32prioritySeperation is not folklore. Its well documented how it can affect your machines latency and performance. It's advance windows settings hidden from the normal user. Connection to cpu vs chipset is not folklore, it's fact that cpu connection is more direct and faster than the southbridge. Southbridge's purpose is to handle slower things so cpu can focus on the faster stuff. Why do the manufacturers even have a set of ports direct to the cpu and a set to the southbridge? There must be a reason....

Is it really nonsense when the reality is that so many people do nothing and do not have issues with latency?
The rest of this is just outdated nonsense. Interrupts interrupt the cpu, nice, sounds like a real problem with a cpu with 16 threads.

[yehaw]

What debloat do you use ?

Just NTLite, that's all you need. Making your own preset is best, as I found a lot of the pre-made presets remove a lot of dumb and unnecessary stuff that will make zero difference. For instance, the default NTLite "gaming preset" removes stuff like the screenshot snipping function.

Then some presets strip hundreds of older drivers. Again, what's the point? To save 500mb space while you run the risk of running into device compatibility issues down the line?

I think this is why a lot of the people write off de-bloating Windows, nobody does the work themselves and use what others provide. Not everyone has the same goals for their setup. I find the vast majority of the pre-made stuff out there is garbage and go way over the top and remove too much, which ends up with things breaking and basic things not functioning. They remove even very lightweight functional tools that are built-in. I've seen some presets that even remove Notepad/Calculator. It's just moronic the levels some of these people go to with some of these configs I've seen shared. I guess if you're starved for disk space on a 32gb hard drive it could make some practical sense?