Jump to content
You must now use your email address to sign in [click for more info] ×

Photo Benchmark 11021 Results


Recommended Posts

  • 2 weeks later...

Hi, I'm totally new here. How can I contribute to this? I have a MacBook Pro 14" (2021) with M1 Max (10 Cores) and 24 cores GPU running on macOS Monterey 12.0.1 ... This is a screenshot of the results from the current macOS beta 1.10.5.270 ... 

1447304976_Screenshot2021-12-07at21_49_47.png.0856a0a9ac966f18a7f53de2e38635e1.png

Link to comment
Share on other sites

On 12/7/2021 at 3:55 PM, metawops said:

Hi, I'm totally new here. How can I contribute to this? I have a MacBook Pro 14" (2021) with M1 Max (10 Cores) and 24 cores GPU running on macOS Monterey 12.0.1 ... This is a screenshot of the results from the current macOS beta 1.10.5.270 ... 

Nice!

image.thumb.png.4c7bd677935c3305d44b4d4720413d36.png

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.0 for macOS Sonoma 14.4, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

  • 2 weeks later...

@MikeTO A good friend of mine was able to perform these tests on his custom hackintosh build.
macOS Monterey 12.1, Intel Core i9-12900K, AMD Radeon RX 6900 XT.

12900k-6900xt.png.047594a2a3d262569a1c7c3b848f8d4a.png

@Andy Somerfield
Just thought it might be interesting for you to see these numbers. Seems like we have new world record here!
Raster (GPU) is 150% faster on RX 6900 XT than M1 Max 32C GPU. Almost 50000 points.

Andy, any thoughts on why we're seeing significant drop in Combined (GPU) score on our machines? Almost 500% lower than Raster (GPU).
Why RX 6900 XT, being 150% faster than M1 Max GPU in Raster (GPU) test and 250% faster in Geekbench Metal has so low Combined (GPU) score?
For M1 machines the difference between these GPU scores isn't that huge. And Combined (GPU) seems to be just 25-30% lower compared to Raster (GPU).

More interesting fact is that even mine RX 580 getting 8600 points in Combined (GPU) and RX 6900 XT has only 10000 points. 16% difference.
When in Raster (GPU) RX 580 has 14500 points and RX 6900 XT has shocking ~50000 points. 345% difference.

Link to comment
Share on other sites

  • 2 weeks later...
  • Staff
On 12/21/2021 at 7:43 AM, Alex M said:

Andy, any thoughts on why we're seeing significant drop in Combined (GPU) score on our machines? Almost 500% lower than Raster (GPU).
Why RX 6900 XT, being 150% faster than M1 Max GPU in Raster (GPU) test and 250% faster in Geekbench Metal has so low Combined (GPU) score?
For M1 machines the difference between these GPU scores isn't that huge. And Combined (GPU) seems to be just 25-30% lower compared to Raster (GPU).

More interesting fact is that even mine RX 580 getting 8600 points in Combined (GPU) and RX 6900 XT has only 10000 points. 16% difference.
When in Raster (GPU) RX 580 has 14500 points and RX 6900 XT has shocking ~50000 points. 345% difference.

Happy New Year!

That's an impressive benchmark score. The reason the combined score is so low, however, is exactly why Apple's M1 chips are so beneficial—since they have UMA (unified memory architecture), there is no penalty when copying data between the CPU and GPU.

The combined score benchmark measures a combination of operations that must be performed on CPU and GPU separately. For example, you may have operations on the CPU (general compositing, vector calculations), then operations on the GPU (raster processing with pixel content). Data has to be copied to and from both devices, which incurs a bandwidth penalty if they are separate rather than unified. That is why you are seeing such a dramatic drop in the combined score: it is factoring in CPU operations, and the memory transfer is clearly quite a bottleneck for the GPU in this instance.

I can give you a practical example using Affinity Photo. Let's say you take an image, then add a few adjustment layers and live filter layers. These will compile kernels that then run on the GPU, so all your compositing is done in 'hardware' and you will see the effect of a faster GPU very clearly.

However, let's say that you then add a vector layer above those layers—for example, a rectangle quick shape, piece of text, or poly curve using the Pen Tool. These vector layers are then going to be processed on the CPU, so the compositing result held in memory must be copied back to the CPU in order to continue compositing. If you then added some more pixel layers, adjustments etc above that vector layer, the compositing data must once again go back to the GPU.

Although it may be less frequent in Photo and Designer, you will continuously run into this scenario with Publisher, since page layout design is the very definition of mixed discipline. At this point, you are at the mercy of whichever component is causing the memory bandwidth bottleneck.

Another advantage of unified memory is that the memory is shared. I do a lot of rendering with blender, 3ds Max and V-Ray etc, and I will often have to render more complex scenes on CPU because they exceed the available VRAM on my GPU (8GB)—especially with V-Ray and archviz scenes. This means I can't take advantage of OptiX rendering on the GPU which is significantly faster. With shared memory, the GPU can just allocate as much memory as it requires rather than having its own discrete pool that you are limited to. I have, on occasion, gone beyond 8GB when compositing in Affinity Photo, so having a shared memory pool of 16/32/64GB is potentially very useful.

A final thing to note: although the M1 scores are technically lower, the increased memory bandwidth as a result of the unified architecture helps everything to 'feel' snappier as well. I now work on an M1 Mac Mini—although the GPU scores around 8000-9000, which seems somewhat pitiful in the face of M1 Pro/Max and the latest discrete GPUs, it still feels incredibly quick with the majority of everyday operations, and all the Affinity apps have some very good optimisation which helps the hardware punch above its technical weight.

Product Expert (Affinity Photo) & Product Expert Team Leader

@JamesR_Affinity for tutorial sneak peeks and more
Official Affinity Photo tutorials

Link to comment
Share on other sites

Custom built i9 11th Generation, running at 5GHz, with 128GB RAM

Windows 11 Pro

 

APbenchmark.png

Affinity 2 Universal  Suite
Desktop:  Apple Mac Studio 2022 model (M1 Ultra) 20 core CPU, 48 core GPU, with 128GB RAM, connected to triple 4k monitors
Laptop: Apple MacBook Pro 14" 2021 model (M1 Max) 10 core CPU, 32 core GPU, with 64GB RAM

Link to comment
Share on other sites

  • 2 weeks later...

Mac Mini 16 GB RAM

 

Screenshot 2022-01-17 at 23.15.34.png

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Fun part: Mac Mini is far lower in Benchmark vs. my Win 10 / GTX1080 PC. But it feels dramatically snappier. PC is handicapped by some spinning rust (besides system SSD), and by Windows itself of course. Feels like a dragster doing endless burnouts standing still, whereas a Tesla just runs away.

I had 2 displays (5K and 4K) connected during benchmark, will try again with only one.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

@MikeTO  Here is my iMac 2021 24" with M1 chip OS Big Sur 11.5.

1711351950_ScreenShot2022-01-21at3_57_43PM.png.d8f0c6956d05cff2d7ff9c5ad29196a9.png


24" iMAC Apple M1 chip, 8-core CPU, 8-core GPU, 16 GB unified memory, 1 TB SSD storage, Ventura 13.6.  Photo, Publisher, Designer 1.10.5, and 2.3.
MacBook Pro 13" 2020, Apple M1 chip, 16GB unified memory, 256GB  SSD storage
,  Ventura 13.6.   Publisher, Photo, Designer 1.10.5, and 2.1.1.  
 iPad Pro 12.9 2020 (4th Gen. IOS 16.6.1); Apple pencil.  
Wired and bluetooth mice and keyboards.9_9

Link to comment
Share on other sites

  • 4 weeks later...

@MikeTO Thank you!

CPU: AMD Ryzen 7 3700X (stock)
GPU: NVIDIA GeForce GTX 1060 6GB
OS: Windows 10 Pro 19044.1288

Ryzen_7_3700X_.png

Link to comment
Share on other sites

1 hour ago, telemax said:

@MikeTO Thank you!

Ryzen 7 3700X (stock)
Windows 10 Pro 19044.1288

Which Intel processor do you have? It's too bad the benchmarking tool couldn't gather that automatically. Thanks.

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.0 for macOS Sonoma 14.4, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

5 hours ago, MikeTO said:

Which Intel processor do you have?

He already wrote that he used an "AMD Ryzen 7 3700X" CPU.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

CPU: AMD Ryzen 7 5700G (stock)
GPU: AMD RX Vega 8 (CPU integrated graphic)
OS: Windows 10 Pro 19042.1526

Ryzen_7_5700G_.png.fd9db1fe2e90bba1898071c245b14ddf.png

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.