|
|
In article <37235c9d.0@news.povray.org> , "Thorsten Froehlich"
<fro### [at] charliecnsiitedu> wrote:
> In article <37234e00.0@news.povray.org> , "Thorsten Froehlich"
> <fro### [at] charliecnsiitedu> wrote:
>
> Please ignore these numbers, they do ***not*** represent results with the
> same settings (for some reason AA wasn't on...). Sorry!
And here are the corrected numbers:
Test 1:
Time For Trace: 0 hours 0 minutes 5.0 seconds (5 seconds)
Total Time: 0 hours 0 minutes 5.0 seconds (5 seconds)
Test 2:
Time For Parse: 0 hours 0 minutes 2.0 seconds (2 seconds)
Time For Trace: 0 hours 1 minutes 5.0 seconds (65 seconds)
Total Time: 0 hours 1 minutes 7.0 seconds (67 seconds)
Test 3:
Time For Trace: 0 hours 0 minutes 22.0 seconds (22 seconds)
Total Time: 0 hours 0 minutes 22.0 seconds (22 seconds)
Test 4:
Time For Trace: 0 hours 5 minutes 42.0 seconds (342 seconds)
Total Time: 0 hours 5 minutes 42.0 seconds (342 seconds)
Test 5:
Time For Trace: 0 hours 0 minutes 20.0 seconds (20 seconds)
Total Time: 0 hours 0 minutes 20.0 seconds (20 seconds)
Test 6:
Time For Trace: 0 hours 10 minutes 16.0 seconds (616 seconds)
Total Time: 0 hours 10 minutes 16.0 seconds (616 seconds)
Test 7:
Time For Trace: 0 hours 0 minutes 41.0 seconds (41 seconds)
Total Time: 0 hours 0 minutes 41.0 seconds (41 seconds)
One note on test 5 and 6: Mac compilers can optimise the lathe code much
better and are therefore much faster than PCs.
One major reason why (even when very few memory allocations occure) the Mac
version is slower is the way POV-Ray represents colors, vectors and almost
all basic types: arrays. The compilers do _not_ manage to use the 32
floating-point registers, instead they nearly always generate load/store
instructions so all the RISC benefits are gone :-(
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: Tho### [at] csicom
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|