- Oct 9, 1999
- 4,378
- 2,256
- 136
Back in 2018 ElFenix posted the original Handbrake Benchmark Thread. I thought it was cool so I started updating the thread with a results table. With his permission I'm posting an update to that thread. If you want to participate we're going to tighten up the testing methodology (see below) so the results provide data better for analysis.
I'll update the second post of this thread periodically with results.
The test file:
sdifox said:
et voila. we can all host the file and round robin it
LG New York HDR UHD 4K Demo.zip
drive.google.com
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
Don't forget to turn on logging in Handbrake so you can retrieve your time. Tools>Preferences>Advanced>Logging
Once this current version is replaced you'll be able to access this version from the following link.
HandBrake: Nightly Builds
Nightly builds 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.
More info on "effective" vs "instant" clock: https://www.hwinfo.com/forum/threads/effective-clock-vs-instant-discrete-clock.5958/
3. Report "Total CPU Usage" (also from HWinfo)
4. Report your encoding time, CPU Model, and RAM specs (amount, speed, latency)
I'll update the second post of this thread periodically with results.
The test file:
sdifox said:
et voila. we can all host the file and round robin it
LG New York HDR UHD 4K Demo.zip
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
Don't forget to turn on logging in Handbrake so you can retrieve your time. Tools>Preferences>Advanced>Logging
Once this current version is replaced you'll be able to access this version from the following link.
HandBrake: Nightly Builds
Nightly builds 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.
More info on "effective" vs "instant" clock: https://www.hwinfo.com/forum/threads/effective-clock-vs-instant-discrete-clock.5958/
3. Report "Total CPU Usage" (also from HWinfo)
4. Report your encoding time, CPU Model, and RAM specs (amount, speed, latency)
Last edited: