WinRar seems to especially dislike my Reaper based workload, or rather the other way around, as WinRar interrupts Reaper even more.Īudio and Video are two very special cases that justify some extra explanation.Īudio drivers do not stall, regardless of the audio buffer size being used. Programs that do not interrupt their processing include: Ableton Live, MediaPlayerClassic, HWinfoīoth WinRar's and 7-Zip's benchmark throughput drop considerably during stalls. ![]() Programs that interrupt their processing include: WinRar, 7-Zip, Foobar2000, Firefox (Youtube HTML video output), Furmark If a program kept processing uninterrupted then the Delta increases on the very next tick right after the stall. If a program interrupted its processing during a stall then the CPU cycles Delta decreases on the very next tick right after a stall. ![]() What Delta means is that when you measure over the span of a second then the Delta is the amount of cycles that happened during that second. The CPU cycles Delta is especially interesting, because it tells us whether a program interrupts processing during a stall or not. Additionally some but not all processing seems to stop during that time, which I reported wrongly before when I claimed that the whole system stops.įirst of all, both the suspension of graphic output and the partly ongoing of background processing can be measured! It's important to note that time-counters seem to roll on regardless of any stalls, which in turn allows software to keep measuring average CPU load, CPU cycles (+delta) and context switches (+delta) and frames per second. Both the GUI/graphic output and keyboard/mouse input are suspended anywhere between a short blip and several seconds (I measured up to around 4). Well, I took a much closer look at those "freezes" again, which I called stalls, but they are the same thing for what we talk about. To make sure that this is not an issue of Reaper (DAW software) I ran my test on an 8 year old 4-threads laptop and there it worked as expected, aka the software stalled when the core was overutilized while the rest of Windows remained usable. It's worse than what I have seen from running ITB and ITB can even run smoothly without stalls under the same circumstances. This also happens in Safe Mode and without using an actual audio driver (null device). My 16 thread CPU is literally turned into a 1 thread CPU for this kind of workload. I tried various CPU core affinities and power schemes, different memory frequency and timing settings, all to no avail. On top of that I did a Clear CMOS and replaced the NVidia GPU driver with the Microsoft standard one. I uninstalled HWinfo and did not run any other software that reads out temps and such. Even processes set to run at Realtime (31) priority get interrupted, all the while neither DPC or interrupt latencies can be measured to increase. That's 15 logical cores being unused and you still can watch graphic elements being built up from top to bottom and input (keyboard/mouse) being heavily broken. ![]() Turns out that even a single logical core being fully (over)utilized by Reaper leads to extreme system stalls close to making it unusable. Up to now I mostly only put time into learning about Ryzen's general operation, compatibility and overclocking, but now I checked DAWBench in Reaper (BIOS 9920). The CPU stress stalls that some people (including me) experience with stress tests are even worse than I thought.
0 Comments
Leave a Reply. |