"Benchmark" Thread for Gigapixel Redefine/Recover

I wanted to get a rough overview over the speed of the Redefine and Recover models in Topaz Gigapixel with various hardware. Since there is no benchmark built-in (as we have in TVAI), I quite randomly chose two images, a low-res and a higher-resolution 12MP one.

So here are the times:
Mac Studio M2 Ultra 24 CPU cores / 60 GPU cores, 64 GB RAM; Gigapixel 8.1.1

  • Recover 2x
    low res: 10m 47s
    high res: 6,5 hours
  • Redefine 2x Creativity 3, all settings default
    low-res: 1m 51s
    high-res: 30m 16s

The original images used are here:
Archiv.zip (3.6 MB)

So feel free to test yourselves and report your rendering times / hardware.

3 Likes

Windows 11 PC I9 64GB RTX 4090 24GB

Recover 2x
Low Res 1m 6 secs
High Res 13m 42 secs

Redefine 2x Creativity 3
Low Res 0 mins 15 secs
High Res 3 mins 20 secs

2 Likes

OK, so this really is a magnitude faster than on my rig!

P.S.: As TVAI, TPGP doesn’t seem to be anywhere optimized for AppleSilicon - it’s often only using about 60Watts in total for the whole system, not really using neither GPU cores, nor CPU and even only 2 Watts for Neural Engine (while I know from TVAI that Neural engine can consume over 20Watts in use)

Model Name: Mac Mini
Model Identifier: Mac16,10
Model Number: MCYT4LL/A
Chip: Apple M4
Total Number of Cores: 10 (4 performance and 6 efficiency)
Memory: 24 GB

Low-res Redefine: 5’50
Low-res Recover: 19’55"

Hi-Res Redefine: I stopped after an hour
Hi-res Recover: too long to bother!

So there is no performance advantage with an M4 over an M2 Ultra. I have no idea how to measure things like wattage etc. to know whether full advantage is being taken of the neural engine.

1 Like

Sorry I misread your post and deleted mine, but before you had read it!

I am curious whether TPAI Super Focus makes better use of the M-series neural engine. Here are my results for jo.vo’s hi-res image (SF entire image, all settings minimum)
Calculating ETA: 34"
Predicted ETA: 12 min
Actual time: 9’30"

Windows 11 PC i9-14900k, 64GB DDR5 RAM, RTX 4070 Ti

Recover 2x
Low Res 1m 30s
High Res 21m 12s

Redefine 2x Creativity 3
Low Res 23 sec
High Res 5m 11s

1 Like

Intel Core i9 13900K limited to 5.5 Ghz, 300 A IccMax, 90 °C max. temp. + 32 GB DDR 5 @ 6 Ghz + ASUS ROG STRIX OC RTX 4090. GPU power consumption up to 500 W on full power during test omg. :eyes:




2 Likes

13700k, 64GB DDR5 , RTX 4070

Recover 2x: Low Res 1m 46s

2025-01-14_150307

Redefine 2x: Low Res 25s

2025-01-14_151039

1 Like

I am not seeing that splash screen with rendering time on my Mac!


Probably because the rendering times are cr*p anyway.

The message box appears when using the ‘Preview Entire Image’ button.

Additionally, I wish the developer would include the render time in the Export dialog as well.

1 Like

Thanks. You are right.


Rubbish timings always with these generative features on the M-series Macs

As @lhkjacky said: this comes up after you use the preview entire image button.

Which is what I always use first anyways as the results of those generative models are quite unpredictable and so I only save the result when I like it ( thus not having to delete the output file if the result was crap).

No fear: after previewing the whole image you can save the result in seconds through the export dialog without it needing to be reencoded.

16GB RAM, RTX 3090, i9-12900k
Low res
Recover x2: 1m 45s
Redefine x2 Creativity 3: 1m 02s

1 Like

Strange. Now I get quite a bit shorter times:

  • Recover 2x
    low res: 10m 47s
    high res: still to be evaluated

  • Redefine
    low res: 1m 51s
    high res: 30m 16s
    I edited the first post for those recent numbers.

I use Gigapixel 8.0.2 now as 8.1.1 has the bug with sometimes broken redefine renderings - but I shortly tested this before and there was no real difference in speed between those two GP versions.

The only other change there was is that I’m now on Sonoma 15.3 Beta (and, of course needing a restart for that to install). So, did Apple change something that leads to those faster times in Sonoma 15.3 - or did something get stuck before and was cured by the reboot?
The numbers look a bit as if the computer was stuck in power saving mode - but then again, if I turn on power saving mode now there’s no real difference in rendering speed of Redefine/Recover :thinking:

Maybe someone other with still MacOS 15.2 can test this before/after going to 15.3 (beta) to verify this. And: if you get slow rendering speeds it might be worthy trying a reboot (according to that old Chinese saying: “reboot is good” :joy:)

Model Name: Mac Mini
Model Identifier: Mac16,10
Model Number: MCYT4LL/A
Chip: Apple M4
Total Number of Cores: 10 (4 performance and 6 efficiency)
Memory: 24 GB

I am still running 15.2 and still getting poor timings (although the actual results can be good on some of my old slides)

Low res image:
Redefine 5m60s (sic!)
Recover 20m14s

Recover is no longer worth bothering with, at least on JPGs.
I am not even going to attempt to process the high res image. It would take way too long.

1 Like