GPU benchmarks - values only
Here is the idea of collecting internal C1 GPU benchmarks in one place right here in this topic. So if someone needs to upgrade the GPU or make new C1 workstation there will be useful information to make the right decision.
I suggest to write every post using the following format:
- Computer model (if any)
- Benchmark score
- GPU model
- GPU driver version
- CPU model
- OS version
- C1 version
I think this is the most significant information about hardware and software that can affect GPU performance in C1 benchmark. If someone thinks this format needs to be updated - please write. Maybe CPU & OS information is excessive?
Some words about internal C1 GPU benchmark, if someone doesn't know about it. Everytime when the C1 starts, it determines capabilities of GPU and makes some kind of benchmark. This bench is specific for C1 and shows how well the GPU is suited to speed up C1 workflow (adjusting images with no time lags and fast exporting). Results of the bench are stored at text log file, that can be found in
- Windows: C:\Users\...\AppData\Local\CaptureOne\Logs\ImgCore.log
- macOS: HOME/Library/logs/CaptureOneIC.log
We need to find the value of "OpenCL benchMark" parameter - and that is the bench result (there may be multiple values in this log file so the last value is needed towards the end of file). Lower value is better. You can also find other important values nearby:
- your GPU model - "OpenCL Device" parameter
- GPU driver version - "OpenCL Driver Version" parameter
It is also very welcomed to add your bench values via this form
Here you can see all collected benches in user-friendly table format.
❗️
Lets make this topic only for our benchmarks in the right format, so other people can easily find the desired information. Please don't make other type of posts (questions, discussions, etc.). I've made another topic only for such discussions, here is the link
-
Bench: 0.930480
GPU: GeForce GTX 450
GPU Driver Version: 388.59
CPU: Intel Xeon E5-1650 @4100MHz (overclocked)
OS: Windows 10 x64, build 1709
C1 Version: 110 -
Mainboard: MSI_X370_XPower_Gaming_Titanium
Benchmark score: 0.050778
GPU model: Sapphire_Pulse_Vega_56 (2nd_BIOS, quiet)
GPU driver version: 19.9.2
CPU model: Ryzen7_1800X
OS version : Windows10_x64, build_1909
C1 version : 12.1.40 -
Benchmark score: .057824
GPU model: GTX 1660S
GPU driver version: 441.20
CPU model: 3770K
OS version: Win 8.1 Pro Version 6.3.9600 Build 9600
C1 version: 20 Build 13.0.0.1550 -
Computer model: Apple 2010 Mac Pro
Benchmark score: 0.038256
GPU model: Nvidia GeForce RTX 2070 SUPER
GPU driver version: 441.66
CPU model: Dual Intel X5680 @ 3.33GHz
OS version: Microsoft Windows 10 Pro (Build 18362)
C1 version: 20 Pro (Build 13.0.0.155)0 -
garrison wrote:
Hi everyone!
Here is the idea of collecting internal C1 GPU benchmarks in one place right here in this topic. So if someone needs to upgrade the GPU or make new C1 workstation there will be useful information to make the right decision.
I suggest to write every post using the following format:- Computer model (if any)
- Benchmark score
- GPU model
- GPU driver version
- CPU model
- OS version
- C1 version
I think this is the most significant information about hardware and software that can affect GPU performance in C1 benchmark. If someone thinks this format needs to be updated - please write. Maybe CPU & OS information is excessive?
Some words about internal C1 GPU benchmark, if someone doesn't know about it. Everytime when the C1 starts, it determines capabilities of GPU and makes some kind of benchmark. This bench is specific for C1 and shows how well the GPU is suited to speed up C1 workflow (adjusting images with no time lags and fast exporting). Results of the bench are stored at text log file, that can be found in- Windows: C:\Users\...\AppData\Local\CaptureOne\Logs\ImgCore.log
- macOS: HOME/Library/logs/CaptureOneIC.log
We need to find the value of "OpenCL benchMark" parameter - and that is the bench result (there may be multiple values in this log file so the last value is needed towards the end of file). Lower value is better. You can also find other important values nearby:- your GPU model - "OpenCL Device" parameter
- GPU driver version - "OpenCL Driver Version" parameter
It is also very welcomed to add your bench values via this form
Here you can see all collected benches in user-friendly table format.
❗️
Lets make this topic only for our benchmarks in the right format, so other people can easily find the desired information. Please don't make other type of posts (questions, discussions, etc.). I've made another topic only for such discussions, here is the link
-2 -
home build
Bench: 0.034328
GPU: GeForce RTX 2080 super
GPU Driver Version: 441.66(studio driver)
CPU: Ryzen 3960X
OS: Windows 10 x64,
C1 Version: 200 -
Lenovo P70
XEON E3-1505M @ 2.8Mhz
Quadro M4000M graphic card with 442.23 latest driver
Intel P530 graphic card with 27.20100.7988 latest driver
32GM RAM
W10 V2004 x64
C1 20.0.40.153296 (dev 0 : Quadro M4000M)
0.588771 (dev 1 : Intel(R) HD Graphics P530)
If the value are the seconds to complete the benchmark, then everything looks good,
Should the benchmark show higher values are faster then there is something terribly wrong...
Chris0 -
Home Build
Bench: 0.024800
GPU: Radeon VII (gfx906)
GPU Driver: 3004.8 (PAL,HSAIL)
CPU: Ryzen 3900X
OS: Windows 10 x64 Pro
C1 Version: 12Custom GPU-Settings (Fan cooling, no water cooling)
32 GB RAM overclocked to 3800 MHz CL160 -
Any Apple M1 user?
0 -
@Whitesnake I saw a thread on reddit with a MBP M1 user, looks pretty promising: https://www.reddit.com/r/captureone/comments/jw28uc/capture_one_on_macbook_pro_m1/
0 -
Computer model: Mac Pro (Late 2013)
Benchmark score: 0.150775
GPU model: 2x AMD FirePro D300 2GB
GPU driver version: 1.2 (Oct 29 2020 23:01:08)
CPU model: 3.7 GHz Quad-Core Intel Xeon E5
OS version: macOS Catalina 10.15.7 (19H15)
C1 version: 20 Pro (Build 13.1.3.9)0 -
Computer model: MacBook Pro 13" (Late 2020)
Benchmark score: 0.229
CPU model: M1
Ram: 16GB
SSD: 1TB
OS version: macOS Big Sur 11.0.1
C1 version: 20 Pro (Build 13.1.3.9)0 -
Just before going out to buy a Mac Mini M1
Computer model: Mac Pro (Late 2009)
Benchmark score: 0.078773
GPU model: AMD Radeon RX Vega 64 Compute Engine
GPU driver version: 1.2 (Oct 29 2020 23:01:08)
CPU model: 2 x 3.5 GHz 6-Core Intel Xeon
RAM: 64GB
OS version: macOS Mojave 10.14.6 (18G6042)
C1 version: 20 Pro (Build 13.1.3.9)0 -
Computer model: HP zbook G7
Benchmark score: 0.054136
OpenCL Device 0 : Quadro RTX 5000
OpenCL Driver Version : 452.57
CPU: GenuineIntel [Intel(R) Xeon(R) E-2286M CPU @ 2.40GHz]
RAM: 128GB
OS version: Windows 10
C1 version: 20 Pro (Build 13.1.3.13)
SSD 2x 970Pro Raid 00 -
Bench: 0.018980
GPU: AMD RX 6700XT
GPU Driver: 19.6.3
CPU: AMD R7 2700
OS: Win10 Pro 64 B19044
C1 Version: 15.4.0.160 -
Bench: 0.034600
GPU: AMD Radeon Pro vii
GPU Driver: Pro 22Q4
CPU: AMD Threadripper pro 3975wx
OS: Win 11 Enterprise
C1 Version: 16.10 -
- Computer model (if any): Self Assembled
- Benchmark score: OpenCL Benchmark : 0.096440 (wall:0.173025) / GPU acceleration benchmark : 0.098600
- GPU model: AMD RX480 (Gigabyte Radeon RX 480 G1 Gaming 8G)
- GPU driver version: AMD software 22.10.3 (Driver 22.20.29.04 | AMD Windows driver / OpenCL driver 31.0.12029.4013)
- CPU model: Intel i5 6600k
- OS version: Win 10 Pro 64bit version 22H2
- C1 version: 15.4.2.10
0 -
M1 MAX - 0,06 GPU benchmark....i hope that i did it properly, deleting the kernels didn't trigger the HW Acceleration rebuild.
Latest OSx and C1
0 -
Benchmark score: 0.023080
GPU model: RX 6650 XT
CPU model: i7-7700K
OS version: Win 10
C1 version: 16.2.20 -
Bench dedicated GPU: 0.010540
Bench integrated GPU (APU): 0.384000
GPU: RX 6800 XT (OpenCL device: gfx1030)
GPU Driver: AMD Software 23.5.2, Driver 22.40.57.05, Windows driver / OpenCL 31.0.14057.5006 (according to C1 logs: 3516.0 (PAL,LC))
CPU: AMD Ryzen 7 7700X (OpenCL device: gfx1036)
OS: Win 11 ProfessionalN 64bit 22H2
C1 Version: Win.15.4.2.10 (Capture One 22)0 -
Bench: 0.115712 (wall:0.131350)
GPU: Nvidia GeForce GTX 1010 6 GB
CPU: Ryzen 5 3600
OS: Windows 11
C1: 16.2
0
Please sign in to leave a comment.
Comments
51 comments