[Req] Preset for decreasing and stabilizing DPC

A

aviv00

Active Member
Mostly for Gamers and Musicians

I notice Server 2022 or 2025 beta have low DPC, around 40-60 micro seconds
while LTSC 2021 have around 100 micro seconds
but not that stable as Server

is there list or preset for remove software-ish drivers impacting DPC

thx

edit:
checked with lateency mon
i think its Wdf01000 driver

Moderator note - more discussion on this post can be found over here on a related thread.
 
Last edited by a moderator:
Hellbovine said:
There was another forum I read where someone was having the same issue on dell laptops. It's probably because of the "Thermal" driver that laptops have installed. I know HP has that driver in their laptops, and it sounds like Dell might too (along with installing a lot of "Dell" services that can cause problems). So this is probably all likely to be laptop-related issues it seems.
Click to expand...
We don't need no stinking drivers, literally...

 
Clanger said:
i think server wins because it doesnt have the desktop experience pack installed which greatly increases the resources usage bringing it closer to regular client editions.
Click to expand...

GamerOS Windows 10 & 11 DIY Preset

There was an MVS collection which had that ISO if I'm not mistaken... yes, it does. Do you want a PM or should I post it here? I had to leave LTSC 2019 behind because of controller support, as old controllers broke and had to be replaced.
www.ntlite.com www.ntlite.com
 
In a nutshell, he's correctly tuning the gap in low/high-water marks for a specific memory cache.

The incorrect application of caching can hurt system performance by adding what users see as "stuttering". Many features in OS optimization require delaying expensive operations (copying memory, writing to disk) until the last possible moment, in the hope some of that won't be needed. Data is stored in the cache, but it's not infinite in size. When the cache is full, it must be emptied to make room.

What controls the speed and impact of cache flushing is the low- and high-water marks. The high-water mark is the setting where the OS recognizes it must take immediate (and unscheduled) action. Cache is emptied until it reaches the low-water mark, and the cycle repeats itself.

When size of the gap between high and low is too wide, you get behavior where the cache takes longer to fill but then requires a huge spike to clear the backlog. By moving the high and low thresholds closer, cache gets flushed more often but each flush is smaller.

"Real-time" performance is less about raw CPU power, but smoothing out the spikes.

PS - The same problem applies to the obsession with event logging. Event logs are buffered in memory, and written to disk. If you have too many events created, or the caches are too large, flushing logs will cause "stutter".
 
all of this is way above my pay grade but i can get windows to flatline in task manager pretty easily, a small blip here and there and windows is, well it feels fast.
 
You must log in or register to reply here.
Back
Top