Acolyte of the Butterfly
Posts: 102 from 2003/5/19
To cut the blahblah short, I tried to do summary with blender versions that are in the same ballpark:
With blender 2.49 or 2.48 & dualcore:
120s blender 2.49 G5 2.3Ghz Dualcore
121s blender 2.49 G5 2Ghz Dualcore (erroneously reported singlecore?)
127s blender 2.49 G5 3Ghz Dualcore (erroneously reported singlecore?)
206s blender 2.48? x1000 1800Mhz Dualcore
Then with blender 2.49 or 2.48 & singlecore:
223s blender 2.49 G5 2.3Ghz single core
234s blender 2.49 G5 2.1Ghz single core
235s blender 2.49 G5 3Ghz SingleCore
325s blender 2.49 PowerBook 1667Mhz
331s blender 2.49 PowerBook 1667Mhz
420s blender 2.48? x1000 1800Mhz Single core
425s blender 2.48a PowerBook 1500Mhz
540s blender 2.48 MacMini 1420Mhz
591s blender 2.48 A1XE 1000Mhz
1180s blender 2.48 SAM440 800Mhz (AOS4)
With same blender version G4 is slower than G5, but faster than PA6T.
Performance scaling etc.:
G5-2300single vs G4-1667 - 1.3 x Mhz - 1.4 x result - G5 better
G5-2300single vs PA6T-1800single - 1.28 x Mhz - 1.88 x result - G5 better
G4-1667 vs PA6T-1800single - 1.08 x Mhz - 0.77 x result - G4 better
G4-1667 vs PA6T-1800dual - 1.08 x Mhz - 1.6 x result - PA6T is better
The last part shows PA6T advantage, one day, after AOS is updated to use both cores. (it seems G5 does not scale as well with multiple cores, neither should G4)
(not that any of this would make x1000 pricing more sensible towards end user)
For blender, what ever PPC one uses on the designer/modeler, one would/should consider x86 render farm for speedup, instead of G5 or PA6T machine, IMO.
[ Edited by KimmoK 07.05.2012 - 11:29 ]