|
![](/i/fill.gif) |
Dennis Clarke <dcl### [at] blastwave com> wrote:
: Clearly the Sparc v8plusa is the winner here. It was compiled with options
: -fast -xarch=v8plusa -Xa. I recompiled the binary with the following options
: just to be sure
: -dalign -fsimple=0 -xO4 -ftrap=%none -libmil -s -temp=/tmp/compiler -v -Xa
: -xarch=v8plusa and that resulted in Total Time: 0 hours 2 minutes 32.0
: seconds (152 seconds)
AFAIK the option -fast turns on the optimal flags (or what it thinks are
the optimal flags) for the target architecture (besides using -xO5). Probably
the flags you used in that latter case are not the optimal for the CPU and
that explains the 15 seconds difference.
And by the way. You should never restrict your benchmarks to just one
POV-Ray file, but you should always test with several files which use
different aspects of POV-Ray. Different features the optimized differently
with the several options and CPU targets.
I recommend you to test at least with POV files like:
- A scene which is slow to parse but very fast to render.
- A scene which doesn't take any considerable memory, but takes time to
render.
- A scene which takes huge amounts of memory (eg. several tens of megabytes)
and render time.
- Perhaps scenes which test individual features of POV-Ray, like lighting,
several types of primitives, meshes, complex textures and so on.
Judging based on just one simple scene may give wrong results in some
cases.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
![](/i/fill.gif) |