Tested the U/F/M clock settings on AM5 a bit better
Theres definitely some hidden math at work, and that makes it very hard to tell people what clocks to use.
Theres nothing between 1800 and 2000, so it's 1800/2000/2033/2066/2100+
That said, the loss from going *TOO HIGH* is far worse than just staying at 1800 sometimes
Focus on the Memory latency only here, as that's what is being tested
Fclk: 2133 = 118.5 ns (Memory read and write tanked massively here)
Fclk: 2066 = 72.9 ns
Fclk: 2033 = 71.8 ns
Fclk: 2000 = 72 ns
Fclk: 1800 =72.7 ns
1800 gave a lower or equal result to 2066 in many of the test runs
For DDR5 6000, the answer is simple:
2033 is the best, 2000 is second best, and 1800 is perfectly fine - especially if it resolves slow boot/cold boot issues.
Going for maximum speeds above 2033 is very likely NOT worth it, unless your RAM speed is higher too.
This is whats thrown me off with a lot of what people have been suggesting, because there are far too many people saying "clock as high as you can go" and the performance loss from doing so goes from 'trivial' to "nailgun to the testicles" very very easily
With the slow boot issues some people have, is shaving 1ns from 1800 to 2000 worth it on those systems? My vote goes to definitely not. Tune in lower voltages and timings instead.
I'll test this with 7600MT/s soon, to see if it's just 2033 being the best value or if it maths with the RAM speed
But I don't turn settings off just to get a bazillion FPS.
I'm only talking about turning things down to stay within your refresh rate, 60Hz users wont have to do anything here, but 144 and up definitely will, no matter the harwdare.
My brother with his Gsync ultimate display and its support of 1Hz means he can handle anything smoothly, while Freesync 2 displays with a 48Hz minimum are entirely different
I could word it better as "I don't know anyone who'd run maximum settings rather than an acceptable frame rate" (With acceptable coming down to the display, usually)