3D rendering 1/2 (LuxMark and Blender@Cycles)
Without application/computational tests, graphics card tests would be incomplete. Therefore, we will focus on this area outside of gaming that most hardware magazines neglect. We understand the reasons, there are several of them, but even so, it is possible with a little effort to make at least a few measurements. So hopefully they will also help multimedia creators in choosing the right graphics card.
LuxMark
Test platform benchmark; API OpenCL; no extra settings.
Blender@Cycles
Test platform render BMW and Classroom; renderer Cycles, 12 tiles; extra settings are OpenCL for Radeon and CUDA for GeForce. The way most people will use it. OpenCL with GeForce is always slow because path tracing does not support GPU acceleration and is computed by the CPU. Nvidia OptiX is tested separately on supported cards (GeForce RTX) and the results are plotted in a separate graph.
- Contents
- Methodology: performance tests
- Methodology: how we measure power draw
- Methodology: noise and sound measurement
- Methodology: heat tests
- Test rig
- ComputeBench (OpenCL)
- ComputeBench (CUDA)
- SPECviewperf 2020 and SPECworkstation 3
- FLOPS, IOPS and memory speed tests
- 3D rendering 1/2 (LuxMark and Blender@Cycles)
- 3D rendering 2/2 (Blender@Radeon ProRender a Eevee)
- Photo editing
- Broadcasting
- Password cracking
- GPU clock speed
- GPU and VRAM heating
- Net graphics power draw
- Analysis of 12 V subcircuit power supply
- Analysis of 3.3 V subcircuit power supply
- Noise level
- Frequency response of sound
- Conclusion
