here are some statistics.
This is the same scene, in different world resolutions(more data calculated in
some) and in the different output forms(checker and mesh)
I'll post the images in .jpeg(coming here)
---
Ran with povray 3.1e watcom compile.
p166MMx, overclocked to 200.
win 95, 64Mb RAM (win uses 32 of those)

The mesh is really only one object, but I've listed it as all the triangles.

If I use AA, the Black/White contrast of the boxes increase the tracing time a
bit(5-7 mins in the 50 grid.)(many sharp edges)
In general, the Boxes are far slower to render than the mesh. It's rather
frustrating, but then :-)
is there a difference if the boxes overlap?(a speed-difference)
I haven't tested for higher than 200x200, since it felt sooo slow, and I have
more fun things to do by the puter :-)

Stats for the 640x480 @AAoff renders:
If you think that the noise looks bad, well... 

Size    Output  Objects       Memory  ParseTime(hms:s)   TotTime(dhms:s)
50x50   Boxes   002 500  001 940 552   00h 00m 43s 043  00h 02m 59s 0179
50x50   Mesh    004 802  001 062 926   00h 01m 07s 067  00h 01m 50s 0110
75x75   Boxes*  005 625  004 277 176   00h 02m 11s 131  00h 07m 16s 0436
75x75   Mesh    010 952  002 157 166   00h 01m 39s 099  00h 02m 27s 0147
100x100 Boxes*  010 000  007 549 677   00h 02m 43s 163  00h 13m 16s 0769
100x100 Mesh    019 602  004 034 847   00h 02m 52s 172  00h 03m 40s 0220
150x150 Boxes   022 500  016 899 677   00h 06m 10s 370  00h 25m 57s 1557
150x150 Mesh    044 402  008 420 207   00h 06m 28s 388  00h 07m 19s 0439
200x200 Boxes   040 000  029 989 677   00h 11m 01s 661  00h 47m 39s 2859
200x200 Mesh    079 202  015 939 327   00h 12m 04s 724  00h 12m 57s 0777


* a slight difference in the box output code. no longer overlapping. (bug fix)


-- 
//Spider
        [ spi### [at] bahnhofse ]-[ http://www.bahnhof.se/~spider/ ]
What I can do and what I could do, I just don't know anymore
                "Marian"
        By: "Sisters Of Mercy"

Post a reply to this message