The new OC performs well overall but struggles with synthetic tasks and doesn’t meet expectations. Why?
The new OC performs well overall but struggles with synthetic tasks and doesn’t meet expectations. Why?
You checked timings and bandwidth using Aida64? That tool isn't ideal here since it mainly depends on basic timing data. The updated OC performs better overall. Aida64 tends to shift results between versions, making comparisons tricky unless you stick to the same version before and after. For more accurate memory testing, consider Linpack Extreme or Y-cruncher, which handle memory well regardless of RAM size. Aida64 works fine but isn't great for real memory performance evaluation.
Intel Memory Latency Checker is available, but I’m out of the AIDA64 free trial and prefer something simpler. I ended up using benchmate instead. Please review the changes @RONOTHAN##. Right now I need to rest; I’ve been working nonstop for three days trying to resolve this issue. Not sure what’s wrong with the BIOS settings. MSI labels each VM function differently.
Your bandwidth rose a bit and latency also increased slightly. This might be due to the CAS latency being a bit higher at each frequency compared to your earlier 3333 configuration. Have you considered lowering the channel to CL15? It looks like you turned off gear down mode, so unless MSI altered it in their BIOS update, CAS latency should be fine.
It seems odd that CL15 at 3533 performs better than CL14 at 3333. I didn’t realize the oddities of AMD’s odd CAS latencies.
Im on Hynix CJR/DJR though, not Samsung B. Anyway, ive tested this new timing, and also adding linpack number by @WereCat idea. Have a look. As you can tell its not that much of a change but the performance is noticeable in synthetics and isnt run-to-run error. Y-Cruncher 1B: 50.5s PyPrime 2B: 14,8 Handbrake: 04m03s Linpack: 234,3GFlops