Thank you for the response! It seems as both ISLC & Timer Tool also have no effect here, I did however find out that by using an somewhat older version called "DPC Checker" to measure DPC I was able to somehow "force" the timer down to 1000us. I have no idea about the techinical stuff that goes behind this, as I'm farily new to "tech" in general. But this does not seem much of a fix, and more of a band-aid. I'd like to figure out why it's not at 1000 by default, preferably without having to re-install the OS hahaRealNC wrote: ↑24 Sep 2022, 04:41Try https://github.com/tebjan/TimerToolOnlyForThemMoment wrote: ↑23 Sep 2022, 17:31That's very interesting! Thank you for your help in clearing that up for me. And yes, it seems as it's not changing during gaming either.
Kernel timer latency?
-
- Posts: 3
- Joined: 22 Sep 2022, 13:08
Re: Kernel timer latency?
- Attachments
-
- DPC2.PNG (999.88 KiB) Viewed 4477 times
Re: Kernel timer latency?
Interesting. So you're saying opening "DPC Checker" is the only thing you found to be able to force the timer down from the initial higher values? As soon as you close the checker does it revert back? And do you "feel"/notice any difference once the timer value is forced down?OnlyForThemMoment wrote: ↑24 Sep 2022, 14:45Thank you for the response! It seems as both ISLC & Timer Tool also have no effect here, I did however find out that by using an somewhat older version called "DPC Checker" to measure DPC I was able to somehow "force" the timer down to 1000us. I have no idea about the techinical stuff that goes behind this, as I'm farily new to "tech" in general. But this does not seem much of a fix, and more of a band-aid. I'd like to figure out why it's not at 1000 by default, preferably without having to re-install the OS hahaRealNC wrote: ↑24 Sep 2022, 04:41Try https://github.com/tebjan/TimerToolOnlyForThemMoment wrote: ↑23 Sep 2022, 17:31That's very interesting! Thank you for your help in clearing that up for me. And yes, it seems as it's not changing during gaming either.
Re: Kernel timer latency?
I can confirm, I've tried this exact thing with LatencyMon and have the same results and running DPC Checker does force the timer down. And yes, when you close it the kernel reading goes back sky high in the red as shown.Shade7 wrote: ↑28 Sep 2022, 00:30Interesting. So you're saying opening "DPC Checker" is the only thing you found to be able to force the timer down from the initial higher values? As soon as you close the checker does it revert back? And do you "feel"/notice any difference once the timer value is forced down?OnlyForThemMoment wrote: ↑24 Sep 2022, 14:45Thank you for the response! It seems as both ISLC & Timer Tool also have no effect here, I did however find out that by using an somewhat older version called "DPC Checker" to measure DPC I was able to somehow "force" the timer down to 1000us. I have no idea about the techinical stuff that goes behind this, as I'm farily new to "tech" in general. But this does not seem much of a fix, and more of a band-aid. I'd like to figure out why it's not at 1000 by default, preferably without having to re-install the OS hahaRealNC wrote: ↑24 Sep 2022, 04:41Try https://github.com/tebjan/TimerToolOnlyForThemMoment wrote: ↑23 Sep 2022, 17:31That's very interesting! Thank you for your help in clearing that up for me. And yes, it seems as it's not changing during gaming either.
Running DPC Checker on / not running and Timer Resolution (max:.5ms) feels very quick and snappy for me.
Re: Kernel timer latency?
What's a "normal" reading from DPC Checker. First time using this tool. Having spikes to "1000" every few seconds.vhagar wrote: ↑28 Sep 2022, 06:44I can confirm, I've tried this exact thing with LatencyMon and have the same results and running DPC Checker does force the timer down. And yes, when you close it the kernel reading goes back sky high in the red as shown.Shade7 wrote: ↑28 Sep 2022, 00:30Interesting. So you're saying opening "DPC Checker" is the only thing you found to be able to force the timer down from the initial higher values? As soon as you close the checker does it revert back? And do you "feel"/notice any difference once the timer value is forced down?OnlyForThemMoment wrote: ↑24 Sep 2022, 14:45Thank you for the response! It seems as both ISLC & Timer Tool also have no effect here, I did however find out that by using an somewhat older version called "DPC Checker" to measure DPC I was able to somehow "force" the timer down to 1000us. I have no idea about the techinical stuff that goes behind this, as I'm farily new to "tech" in general. But this does not seem much of a fix, and more of a band-aid. I'd like to figure out why it's not at 1000 by default, preferably without having to re-install the OS haha
Running DPC Checker on / not running and Timer Resolution (max:.5ms) feels very quick and snappy for me.
Re: Kernel timer latency?
Issue persists whilst using ultimate performance power plan, USB selective suspend disabled, power savings unchecked for each USB controller, all C-states and power savings full disabled using scewin to check no hidden ones in BIOS etc.. everything.
The only 2 things that seem to change the latencymon kernel timer results are running DPC checker, or while playing around with bcdedit settings. When toying around with bcdedit I noticed that with DPC checker open, the timings would change from 0.5-1 to 0.8 to 1.2.
The only 2 things that seem to change the latencymon kernel timer results are running DPC checker, or while playing around with bcdedit settings. When toying around with bcdedit I noticed that with DPC checker open, the timings would change from 0.5-1 to 0.8 to 1.2.
Re: Kernel timer latency?
Found this documentation that I found quite interesting regarding system timers and their current state. I feel it may be relevant.
https://randomascii.wordpress.com/2020/ ... le-change/
https://randomascii.wordpress.com/2020/ ... le-change/
Re: Kernel timer latency?
Nice catch! Looks like we now need an injector that calls timeBeginPeriod() before the main entrypoint.Vocaleyes wrote: ↑02 Oct 2022, 04:03Found this documentation that I found quite interesting regarding system timers and their current state. I feel it may be relevant.
https://randomascii.wordpress.com/2020/ ... le-change/
Steam • GitHub • Stack Overflow
The views and opinions expressed in my posts are my own and do not necessarily reflect the official policy or position of Blur Busters.
The views and opinions expressed in my posts are my own and do not necessarily reflect the official policy or position of Blur Busters.
Re: Kernel timer latency?
This comment by the user Gerard particularly caught my eye, quoting -
“It is not true, that nothing has changed, if you called timeBeginPeriod in your program all along.
I am writing a streaming application, that used one shot CreateTimerQueueTimer timers to trigger the sending of UDP packets every few milliseconds. Since Win 10 2004 this is broken, my timers only fire after 15ms despite calling timeBeginPeriod(1). I changed it to use timeSetEvent, now it works again, including on Windows 10 2004 and 20H2.
So since the 2004 update CreateTimerQueueTimer() ignores the resolution defined by timeBeginPeriod.
Unfortunately timeSetEvent is desclared obsolete, with a recommendation to use the (now broken) CreateTimerQueueTimer. On the other hand timeSetEvent has been declared obsolete since at least 2008 (earliest mention of the obsolence found in a quick Google search) and it is still around. Hopefully it will stay oder Microsoft fixes CreateTimerQueueTimer.”
“It is not true, that nothing has changed, if you called timeBeginPeriod in your program all along.
I am writing a streaming application, that used one shot CreateTimerQueueTimer timers to trigger the sending of UDP packets every few milliseconds. Since Win 10 2004 this is broken, my timers only fire after 15ms despite calling timeBeginPeriod(1). I changed it to use timeSetEvent, now it works again, including on Windows 10 2004 and 20H2.
So since the 2004 update CreateTimerQueueTimer() ignores the resolution defined by timeBeginPeriod.
Unfortunately timeSetEvent is desclared obsolete, with a recommendation to use the (now broken) CreateTimerQueueTimer. On the other hand timeSetEvent has been declared obsolete since at least 2008 (earliest mention of the obsolence found in a quick Google search) and it is still around. Hopefully it will stay oder Microsoft fixes CreateTimerQueueTimer.”
Re: Kernel timer latency?
It was already given: the documentation now says it's per-process. So an injector is needed so that the timeBeginPeriod() call happens in the game's process itself, not by a another process.
Steam • GitHub • Stack Overflow
The views and opinions expressed in my posts are my own and do not necessarily reflect the official policy or position of Blur Busters.
The views and opinions expressed in my posts are my own and do not necessarily reflect the official policy or position of Blur Busters.