"jr" <cre### [at] gmailcom> wrote:
> "Deepak" <dee### [at] iiitbnet> wrote:
> > I am new to try with Povray application.
> > I am trying to test performance of
> > various compiler like (gcc, clang) on CPU with
> > scenes/advanced/benchmark/benchmark.pov (as suggested here-
> > http://www.povray.org/download/benchmark.php)
> > What I observed is the rendering is finishing in ~1.5 seconds only.
> > So it's difficult to compare the results with various compiler for such short
> > duration.
> > Is there any large data set which runs for considerable time?
> every POV-Ray install comes with a large number of example scenes[*], some of
> which will take a fair amount of time to render; animations too are available.
animations are an interesting choice. i have noticed that an average of the
time-stamps yields a different number from that reported by the program.
perhaps it is system overhead, or perhaps it is just my machines, or maybe the
numbers converge with a large enough sample.
to do animation add at the bottom of povbench.ini
Output_To_File=On ;so you will have files with time-stamps
Cyclic_Animation=off ;;insures it reaches 1.0
i believe without testing that later parameters overwrite earlier ones. if not
so you will have to comment out those earlier variables.
> also, if you "nose around", some of the newsgroups here often contain SDL
> code/scenes provided by other users.
> [*] typically in %INSTALLDIR%/scenes.
> > or what parameter to change on .ini file to run it with considerable time.
> > Thanks in advance for your help,
> > Deepak
changing the ini file might be a better choice for you as opposed to animation.
first to mind is the resolution; the ini specifies a small picture, increasing
it to ten times height and width should increase rendering time a hundred fold.
something like this, again at the end of ini to overwrite original values
you can also increase antialiasing (these are the default values)
Antialias_Depth=3 ;increasing takes longer
Antialias_Threshold=0.3 ;decreasing takes longer
Sampling_Method=1 ;no idea what the effect on time is
however, povbench.pov might not be the best choice for you. it has a fast parse
time and a slow render time. parsing uses only one core; therefore slow,
many-core machines are faster than fewer-core, fast clock machines when you
compare similar cores*hertz. i am not familiar with the standard scenes that
come with povray to advise you which scene files have long or short parse versus
but now the only thing that prompted me to post; what kind of monster machine
are you running that is 100x faster than my best rendering engine (drool)?
Post a reply to this message