|
![](/i/fill.gif) |
Thorsten Froehlich wrote:
>
> While all you say is correct and remains valid, it has to be admitted that
> benchmark.pov has one little bias as it does give a rather heavy weight to
> the noise function due to the clouds.
Heavy use of the noise function is quite common for a typical POV-Ray
scene, even without media, due to procedural textures and geometry. In
a typical isosurface landscape scene it is even more excessive than in
benchmark.pov.
> The reason is that such a comparison is not optimal with the default
> benchmark.pov is that automatic bounding is turned on, which makes the major
> task while rendering searching the bounding volumes. This to a major part
> depends on memory access. It is really a lot of searching, but not so much
> computing at all...
Surely the use for comparing processors is limited by this but for
comparing the performance of whole computers concerning POV-Ray use this
is exactly what's needed - a typical POV-Ray render will spend much time
with memory access (in addition to bounding slabs just think of large
meshes, photon maps, radiosity, image maps).
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 11 Jan. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
![](/i/fill.gif) |