That's not an accurate way of showing the clock frequency either. Windows task manager "Speed" is actually very inaccurate when it comes to Zen unless you dumb it down by running an allcore oc. As I type this, task manager is showing 4.2ghz and yet no cores are effectively over 1.5ghz.
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
HWinfo can give you average CPU frequency during your run.
Moving forward why don't we set some additional test parameters?
1.
Use the following version of Handbrake with the built-in h.265 mkv 2160p60 preset
HandBrake-1.3.3-x86_64-Win_GUI.exe
Once this current version is replaced you'll be able to access it from the following link.
Old Releases of HandBrake
handbrake.fr
2.
Report average effective clockspeed using HWinfo - https://www.hwinfo.com/
I'm sure there are better ways to do this using the logging feature but here's how I did it. I downloaded the portable version, which runs from the exe file.
Run the exe and select "sensors only." You only need this window open.
Minimize the sensors window so you can have it and Handbrake visible at the same time. Select the "average effective clockspeed" line so you can spot it easily. It will highlight.
Note the icon for "reset min/max/average values and timer" in the bottom right area of the window, it's the clock icon.
Start the handbrake but don't start/reset the timer until handbrake is actually encoding video. Record the average effective clockspeed right before handbrake finishes the encode. It should settle in pretty quickly after the encode starts and not change during the encode.
3.
Report "Total CPU Usage" (also from HWinfo)
4.
Report your encoding time and CPU model