AMD Radeon RX 5700 XT Compute Related Benchmarks
As we move along with the GPU testing we felt it was time to clean up our database and results in graphs, we have dropped the Silent and OC results for each card and kept the fresh out of box numbers. Doing so made our graphs much easier to read, many users here at STH do not run cards in those configurations or simply cannot do so in Linux based systems so this was warranted. We still have our test numbers and might revisit those settings later on. We started the cleanup several reviews ago in this series.
Geekbench 4 measures the compute performance of your GPU using image processing to computer vision to number crunching.
Our first compute benchmark we see the Radeon RX 5700 XT achieve results near an NVIDIA GeForce RTX 2080 Super on the OpenCL side. The Radeon RX 5700 XT does not have CUDA capabilities so it does not complete that test. Still, this is an impressive performance at the price point.
LuxMark is an OpenCL benchmark tool based on LuxRender.
With LuxMark results, we find the XFX Radeon RX 5700 XT again performs near the NVIDIA GeForce RTX 2070 to 2080 SUPER GPUs which is impressive. One can also see performance above the Vega Frontier Edition we tested.
These benchmarks are designed to measure GPGPU computing performance via different OpenCL workloads.
- Single-Precision FLOPS: Measures the classic MAD (Multiply-Addition) performance of the GPU, otherwise known as FLOPS (Floating-Point Operations Per Second), with single-precision (32-bit, “float”) floating-point data.
- Double-Precision FLOPS: Measures the classic MAD (Multiply-Addition) performance of the GPU, otherwise known as FLOPS (Floating-Point Operations Per Second), with double-precision (64-bit, “double”) floating-point data.
Here we see performance between the GeForce RTX 2070 Super and standard version. If you want single and double precision FLOPS, the older Vega Frontier Edition is still faster.
The next set of benchmarks from AIDA64 are:
- 24-bit Integer IOPS: Measures the classic MAD (Multiply-Addition) performance of the GPU, otherwise known as IOPS (Integer Operations Per Second), with 24-bit integer (“int24”) data. This particular data type defined in OpenCL on the basis that many GPUs are capable of executing int24 operations via their floating-point units.
- 32-bit Integer IOPS: Measures the classic MAD (Multiply-Addition) performance of the GPU, otherwise known as IOPS (Integer Operations Per Second), with 32-bit integer (“int”) data.
- 64-bit Integer IOPS: Measures the classic MAD (Multiply-Addition) performance of the GPU, otherwise known as IOPS (Integer Operations Per Second), with 64-bit integer (“long”) data. Most GPUs do not have dedicated execution resources for 64-bit integer operations, so instead, they emulate the 64-bit integer operations via existing 32-bit integer execution units.
With AIDA64 GPGPU benchmarks we find the Radeon RX 5700 XT is closer to the NVIDIA RTX 2070 line. There is a standout, 32-bit integer performance figures are well below the GPU’s NVIDIA competitors.
hashcat64 is a password cracking benchmarks that can run an impressive number of different algorithms. We used the windows version and a simple command of hashcat64 -b. Out of these results we used five results to the graph. Users who are interested in hashcat can find the download here.
With hashcat, the Radeon RX 5700 XT drops below the NVIDIA RTX 2060 performance levels. We also note that with hashcat64 v5.0.1 we could not get to run, we used the Beta hashcat v220.127.116.114 for our tests. We mentioned that we would point out the extra steps we needed to get the card running, and this is one of those cases.
SPECviewperf 13 measures the 3D graphics performance of systems running under the OpenGL and Direct X application programming interfaces.
With SPECviewperf we see interesting results, in parts of this benchmark the Radeon RX 5700 XT Graphics Card has excellent performance but falls considerably in others like Maya, SNX, and CREO.
Let us move on and start our new tests with rendering-related benchmarks.