PaintTinJr
Member
I would rather have a solid AMD chip with less heat instead of an up clock to 2Ghz. I don't necessarily want a higher end frequency for bragging rights when a boost clock around 1800mhz to 1950mhz are good enough personally for me.
I tinker a lot with my PC GPU clock and memory frequencies, and to high of a clock frequency will yeild a few unintended problems that are annoying.
For one is the energy bill, but secondly, a high clock doesn't always end up with better performance at all. Stuttering and unstable system freezing suck, especially on pascual GPU'S. Allowing My GPU to hit normal boosts or with slight clock frequencies O'C will run games a helluva a lot better without the heat.
My thinking for 2GHz clocks would be for B/C emulating old PS3 SPU workloads on GPU CUs without code modification per game. Where the modern AMD GPU CUs probably have a 2 fold efficiency of an SPU, but as the SPUs were running at 3.6GHz and probably had access to as much as 200KB data in local store/scratch memory per workload on full mature PS3 software development. By pushing to 2GHz it is maybe possible to subsume the compute and the memory access of those workloads.
Depending on how the software works with PS5, the workloads might be CU clock limited, either where refactoring for parallelism at lower clocks isn’t an option or refactoring is an option, but it increases the resource burden on other things like memory bandwidth or memory storage in a non-linear way, thus making higher clocks the preferred option.
I'm not sure Sony changing clocks is equal to you changing clocks, as you don't have full control over all the drivers, the OS or game source code which might be the cause of your issues.