Issue with AMD Precision Boost performance in gaming environments.
Issue with AMD Precision Boost performance in gaming environments.
I looked through online resources for others experiencing the same issue, but found nothing. It appears the Precision Boost feature isn't functioning in games, even though it works in BIOS and Ryzen Master. When I run Cinbench R20, it successfully boosts to 4.5 GHz. This is unusual since it typically causes a significant performance drop. In my setup, the CPU reaches a maximum of 2.1GHz during games, and the 240mm AIO doesn't seem to cause thermal problems. Any suggestions or insights would be greatly appreciated!
When using a GPU limit, the CPU won't require excessive boosts. Monitor both GPU and CPU usage per thread during gameplay, along with the specific software you're using to check CPU frequency.
I'm tracking performance data using Radeon Software. Right now I'm playing Just Cause 3. With a 2GHz CPU the GPU usage stays under 70%, which shouldn't be an issue. Even after manually increasing the CPU frequency to 4.5GHz, the GPU remains around 92-95% with full settings on 1080p. At 2GHz the CPU usage never exceeds 15%, rising to about 40% when overclocked to 4.5GHz. The GPU temperature is approximately 60°C.
In gaming it doesn't matter what you use overall, just per core. Check CPU speeds with tools like Ryzen Master or HW Monitor. Radeon Software's monitoring has many issues that haven't been fixed yet.
You're right, the issue isn't about usage on either side. It turns out the Precision Boost doesn't function properly in games, and I've tested many titles without success. It seems to activate only when the CPU reaches a specific load level, as seen in benchmarks like Cinebench or stress tests.
Usage patterns aren't the only factor. Your 8Core 16Thread CPU1 thread operating at full capacity accounts for just 6.25% of total load, making it the limiting element here. The overall figure doesn't capture the full picture.
The question refers to a clock located within a central component, but no specific context or object was mentioned.