encoded 1806 frames in 170.24s (10.61 fps), 11820.04 kb/s, Avg QP:29.09
Average Effective Clock screenshot at 93% done.
Which " average " column number you want ... is questionable....
Averages ... of averages ... are not accurate.
This test is not pushing the limits of this chip.
I'm expecting an ALL core OC of 4.65 GHz
( not testing yet )
Will submit when All Core found.
( this is a BOOST score )
Thanks! That's perfect. I added your score to the table. Those Zen 3's really crush Handbrake.
From what I understand from my reading of "Average Effective Clock" it's not an average of an average. From the following link:
It has become a common practice for several years to report instant (discrete) clock values for CPUs. This method is based on knowledge of the actual bus clock (BCLK) and sampling of core ratios at specific time points. The resulting clock is then a simple result of ratio * BCLK. Such approach...
www.hwinfo.com
"It has become a common practice for several years to report
instant (discrete) clock values for CPUs. This method is based on knowledge of the actual bus clock (BCLK) and sampling of core ratios at specific time points. The resulting clock is then a simple result of ratio * BCLK. Such approach worked quite well in the past, but is not longer sufficient. Over the years CPUs have become very dynamic components that can change their operating parameters hundreds of times per second depending on several factors including workload amount, temperature limits, thermal/VR current and power limits, turbo ratios, dynamic TDPs, etc. While this method still represents actual clock values and ratios reported match defined P-States, it has become insufficient to provide a good overview of CPU dynamics especially when parameters are fluctuating with a much higher frequency than any software is able to capture. Another disadvantage is that cores in modern CPUs that have no workload are being suspended (lower C-States). In such case when software attempts to poll their status, it will wake them up briefly and thus the clock obtained doesn't respect the sleeping state.
Hence a new approach needs to be used called the
Effective clock. This method relies on hardware's capability to sample the actual clock state (all its levels) across a certain interval, including sleeping (halted) states. The software then queries the counter over a specific polling period, which provides the
average value of all clock states that occurred in the given interval. HWiNFO
v6.13-3955 Beta introduces reporting of this clock.
Many users might be surprised how different this clock is in comparison to the traditional clock values reported. But please note that this effective value is the average clock across the polling interval used in HWiNFO. "
forums.anandtech.com
Facebook
Twitter