Ryzen master is also quite confusing at times as well (with PBO enabled in bios, it tells me auto OC, not PBO, is enabled?!?)
Auto-OC is the Ryzen Master term for having a Max Boost Override above 0, it is all still PBO.
I've also just begun tweaking IF speed - hit 1866 without changing any voltages. 1900+ causes the host to hang, so I'm likely going to need to figure out what to tweak to try to push it higher. Once I've locked in IF speed, I'll start tightening ram timings, which I could also use a good guide for.
I spontaneously found myself with an Engrish source of info on the topic;
lowest voltage for 3800MT/s is
900-980-1050
VDDP, VDDG, vSOC @ 34ohm procODT
Along with some info on Vermeer having aggressive error-correction on the fabric.
Now, the takeaway is that high FCLKs (above 1900)
work, kind of, but more by the power of error correction - worse performance - than through Just Working.
Apparently, VDDP and VDDG CCD like being matched - but I haven't personally messed with what the implications of it are, and decoupling them works fine?
What I did mess with however, is getting 2000 FCLK to perform better than my 1900 setup.
The things which I found
on my setup;
An IOD voltage of 1.06v or higher (I ended up running 1.08v) is mandatory; 1.00v was horrendously unstable, 1.05v had performance penalties, 1.06v had more or less the same performance as going up to 1.08v.
Just as demonstrated in the ChipHell image, there was "performance scaling" with higher vSOC voltages; up until I set it to 1.285v, at which point it performed the same as 1.275v.
Handy tool: You can use the Latency Graph function of DRAM Calculator to see if your vSOC/IOD are too low;
This is an example with too little, and the L3 cache portion of the CPU jumps way up in latency compared to where it's supposed to be;
Here's the same CPU settings, the same memory settings, just
almost enough vSOC and enough vIOD.
Why
almost enough vSOC? Well, because as the first image says; the memory controller likes low (SOC) voltage.
I'm running a cranked b-die setup at 1.63v -
on top of it being dual-rank, then also whacking a crazy voltage into the SOC.
It resigned after telling me to go **** myself at vSOC 1.275
So it ended up being this;
And here's the kicker
in my case;
The latencies, at the same CPU clockspeed, are functionally equivalent at 1.265vSOC - and mildly better at 1.275v+, but those couldn't run the memory settings
)
Except at 1900 I get to run much less insane voltages on the internals of my CPU!
ergo it was a complete waste of time and effort, for me at least xddddddddddddddddd
If you're running less intensive memory setups though, there's probably some juice to find there.
