I think that in cases where the current benchmark is too slow you should
render it as an animation with 10 or 100 or even 1000 frames and then divide
the total render time with the number of frames rendered. All the frames
would be the same but that the whole point that makes this method work...
Memory wouldn't be very high, but who says the POV-Ray benchmark has to
measure memory speed anyway.

This solution would be by far the simplest and it would be fully comparable
to test that have already been performed.

...Just a different (and perhaps slightly boring) approach to the problem...

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:    http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users:   http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk

Post a reply to this message