Shortly after running these tests, Adobe released a version of Premiere Pro with GPU-specific rendering optimizations. Additionally, software evolves constantly. A real comparison would need to test several different projects, different features, and different hardware configurations. This is not a head-to-head Resolve vs Premiere comparison. With this workstation having two of the most powerful GPUs you can find, I suspect that this performance difference can be explained by Resolve utilizing the dual Quadro configuration better than Premiere.īut a word of caution: it is only a single data point. Resolve is almost two and a half times faster. In the end, Resolve renders this one minute test project in 76 seconds while Premiere Pro requires 184 seconds. With CPU utilization Premiere Pro scatters the work across many logical cores in a way that evokes randomness more than orderliness. In contrast, GPU utilization under Premiere Pro is a series of spikes. While it seems to ignore the second CPU in the system, it loads all 32 logical cores in the first CPU in a clean, organized fashion. For the CPU workloads, Resolve spreads the work evenly across one processor. Resolve uses the processor in a similarly orderly fashion. The utilization doesn't spike and then drop to zero which is what I typically see when testing Premiere Pro. The percent utilization remains stable throughout the rendering. The second GPU is loaded at a capacity level in the low 40’s. In this multi-stream, 4K rendering test, the first GPU runs consistently close to 50% capacity. Facial Refinement is one of many GPU-accelerated features in DaVinci Resolve 16
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |