Sony Playstation 5 in iGPU - FP32 Performance (Single-precision GFLOPS)

Here we show you how fast the Sony Playstation 5 is in the iGPU - FP32 Performance (Single-precision GFLOPS). Based on the result, you can assess whether this processor is suitable for you. In addition to the clock frequency, the number of CPU cores is also crucial. Please note that these benchmark values can only be achieved if the Sony Playstation 5 is sufficiently cooled, as current processors usually achieve their maximum performance in benchmarks and in practice in turbo mode.
Sony Playstation 5

At a glance

Name: Sony Playstation 5
Family: AMD Ryzen 7 (79)
CPU group: AMD Ryzen 4000G (26)
Segment: Desktop
Generation: 3
Predecessor: --
Successor: --

iGPU - FP32 Performance (Single-precision GFLOPS) - Benchmark results

Apple M2 Max (30-GPU) Apple M2 Max (30-GPU)
Apple M2 Max (30 Core) @ 1.40 GHz
10650
Apple M3 Max (14-CPU 30-GPU) Apple M3 Max (14-CPU 30-GPU)
Apple M3 Max (30 Core) @ 1.40 GHz
10650
Apple M1 Max (32-GPU) Apple M1 Max (32-GPU)
Apple M1 Max (32 Core) @ 1.30 GHz
10600
Sony Playstation 5 Sony Playstation 5
AMD Custom Radeon Graphics (Playstation 5) @ 2.23 GHz
10300
Apple M5 Pro (18-CPU 20-GPU) Apple M5 Pro (18-CPU 20-GPU)
Apple M5 Pro (20 Core) @ 1.90 GHz
10266
Apple M5 Pro (15-CPU 16-GPU) Apple M5 Pro (15-CPU 16-GPU)
Apple M5 Pro (16 Core) @ 1.90 GHz
8213
Apple A19 Pro Apple A19 Pro
Apple A19 Pro (6 GPU Cores) @ 2.00 GHz
8193
Show all iGPU - FP32 Performance (Single-precision GFLOPS) results


More benchmark results for the Sony Playstation 5

Benchmarks help you to realistically assess the performance of a processor. Within a version, the benchmark results of different CPUs are comparable. All results published by us are carefully checked.

We currently support the following benchmarks:

CPU groups

We have clearly divided all processors available in our benchmark database into groups for you. For example, all Intel Core i7 processors can be compared at a glance. In addition, all CPUs of a generation are divided into subgroups.



back to index