Puget Systems print logo


Read this article at https://www.pugetsystems.com/guides/1523
Article Thumbnail

Puget Systems DaVinci Resolve Studio Benchmark

Written on August 26, 2019 by Matt Bach

At Puget Systems, one of our primary goals is to make sure that our customers end up with a fast, reliable workstation that is perfectly tailored to their unique workflow. The main way we do this is by benchmarking a wide range of hardware in DaVinci Resolve (and numerous other software packages) that we then publish in our ongoing series of hardware articles.

However, while this ensures we are selling the right hardware, it does not give our customers a great idea of how much faster a new workstation would be compared to their existing system. To address this issue, we are making our internal Resolve benchmark available for public download so that anyone can compare their own computer to our latest DaVinci Resolve hardware articles.

Puget Systems DaVinci Resolve Studio Benchmark

If you are interested in how your system performs in other creative applications, we care currently working on making our benchmarks available to the public. At the moment, we have the following benchmarks available:

How to run the benchmark

After downloading the benchmark, unzip it to a convenient location - we recommend placing the media test files on the same drive that you store your active project media as storage performance can affect the results.

Before running the benchmark itself, be sure to launch DaVinci Resolve and configure any preferences you want to have set (such as GPU processing mode, GPU selection, etc). After that, run the "Benchmark_Run.exe" file in the root of the benchmark folder. This will allow you to select specific tests to run including:

  • 4K Benchmark - Requires 16GB of RAM and at least 8GB of GPU VRAM
  • 8K Benchmark - Requires 32GB of RAM and at least 20GB of GPU VRAM
  • Fusion - Requires 16GB of RAM and at least 4GB of GPU VRAM
  • Full - Runs all three sets in series. Requires 32GB of RAM and at least 20GB of GPU VRAM

Puget Systems DaVinci Resolve Studio Benchmark Window

When the benchmark is complete, it will give you an "Overall Score" for the type of test you ran. A log file is generated in the benchmark folder that includes these scores as well as the FPS for each individual task. You can compare your scores to those in our DaVinci Resolve hardware articles - just make sure they used the same benchmark version!

What is tested?

Our DaVinci Resolve benchmark looks at rendering with a wide range of codecs at 4K and 8K resolutions as well as performance in Fusion.

Our test media consists of the following resolutions and codecs:

Test Media (59.94 FPS)
4K CinemaRaw Light 4K H.264 150mbps 8-bit
4K ProRes 422 4K ProRes 4444
8K H.265 100mbps 8K RED

For the 4K and 8K render tests, we benchmark 5 different levels of grade:

  • "Optimized Media" - No effects applied in order to simulate the performance when generating optimized media
  • "Basic Grade" - Simple color wheel and similar adjustments with a base grade plus 4 power windows.
  • "OpenFX - Lens Flare + Tilt Shift Blur + Sharpen" - Basic Grade plus four OpenFX
  • "Temporal Noise - Better 2 Frames" - Basic Grade plus a single TNR node
  • "3x Temporal Noise - Better 2 Frames" - Basic Grade plus three TNR nodes using splitter/combiner nodes

The "Optimized Media" timeline is rendered out to MXF OP1A DNxHR LB at 1920x1080 while the others are all rendered out to Quicktime DNxHR HQ at the native resolution of the timeline (UHD or 8K).


This benchmark is designed for DaVinci Resolve Studio 16. While it does technically work with the free edition, the OpenFX and TNR test result in a watermark overlay which may impact performance slightly. In addition, the free edition does not support GPU-acceleration for H.264 media which can result in 20% or more performance loss versus the Studio version.

You will need between 16-32GB of system RAM and a GPU with 4-20GB of GPU VRAM depending on the test selected.

Currently, this benchmark is for Windows only, although we have plans for a MacOS version in the future.

Note that this benchmark is still in BETA. Plug-ins and customized preferences in particular may prevent the benchmark from running properly.

How does the scoring work?

The scoring system used in our benchmark is based on the performance relative to a reference workstation with an Intel Core i9 9900K and NVIDIA Titan RTX 24GB.

The results are grouped according to the codec used, the type of grade performed, as well as a single "Overall Score" that averages the results for each test.

Update Log

Version 0.61 BETA

  • Minor update to fix issue when running the benchmark from a non C: drive

Version 0.6 BETA

  • Replaced H.264 media with 150mbps footage straight from a Panasonic GH5

Version 0.5 BETA

  • First release.

Looking for an DaVinci Resolve Workstation?

Puget Systems offers a range of workstations that are tailor made for your unique workflow. Our goal is to provide most effective and reliable system possible so you can concentrate on your work and not worry about your computer.

Configure a System!


Thanks! Small comment, you should add a line "C:" below the cd command since if you run the batch file from a drive different from C:, it will not cd onto the c: drive to find resolve.exe....

Posted on 2019-08-28 11:14:11

Good call, I didn't even consider that. I'll add that and update the benchmark. Thanks for the suggestion!

Posted on 2019-08-28 17:34:39
Todd Peterson

This is great to have a proper Resolve benchmark, but why no ARRIRAW or arx files in the benchmark? There are a lot of us shooting on Alexa that would love to see it included.

Posted on 2019-09-10 08:21:29

ARRIRAW (and BRAW for that matter) is definitely something we want to include. Right now, we simply don't have the time to actively go out and source test footage that meets all our requirements - primarily full permission to redistribute. If you or someone you know would be willing to help, however, we can add ARRIRAW into the benchmark pretty easily and start including it going forward

What we need are clips that are ~14 seconds long (we only need 12 seconds, but that gives us a bit of extra without making the file too large). A zooming/panning/moving shot of anything with a decent amount of color should work well - we mostly just need things constantly changing in frame and decent amount of different colors so that we can do more with it in terms of grading in Resolve.

We need UHD (or true 4K, either way) clips at both 29.97 and 59.94 FPS.This is an example of the RED footage we are using: https://www.youtube.com/wat... and the H.264 clip we are using: https://www.youtube.com/wat...

If you are interested in helping us out, feel free to reach out to me via email (just to avoid cluttering these comments). mattbach@pugetsystems.com

Posted on 2019-09-10 17:08:11
Todd Peterson

I've been testing on a few different setups with high/low clocks, high/low core counts, Pascal vs. Turing, etc. A couple of observations:
1) The Fusion benchmark appears to be single threaded and thus very sensitive to clock speed. On a 24 core Xeon 8160, due to low clock speeds, I see no difference in score between a 2060 Super and a GTX 1060 6GB.
2) The 4K benchmark does not use more than one processor. Depending on the test it seems to use all cores/threads (24c/48t in my case), but only one of the two processors.

Have you seen these same behaviors?

Posted on 2019-09-14 05:03:26

That is not really the fault of our benchmark - that is just how Resolve behaves in general and is what we see over and over again in our testing: https://www.pugetsystems.co...[]=DaVinci%20Resolve

The only one that sounds a bit odd is Resolve only using one CPU. It should use both, although the overall load will likely be a lot lower on the second CPU.

Posted on 2019-09-16 17:16:08