 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Is there a current standard benchmark scene that is used to determine
parsing/rendering performance? I just upgraded my computer and would like
to see how it does.
Thanks.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3f99dec8$1@news.povray.org>,
"Cris Williams" <CLW### [at] woh rrcom> wrote:
> Is there a current standard benchmark scene that is used to determine
> parsing/rendering performance? I just upgraded my computer and would like
> to see how it does.
benchmark.pov?
(look in scenes/advanced/)
--
Christopher James Huff <cja### [at] earthlinknet>
http://home.earthlink.net/~cjameshuff/
POV-Ray TAG: chr### [at] tagpovrayorg
http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
LOL! Thanks. I guess that was too obvious for me to deal with. Thanks!
"Christopher James Huff" <cja### [at] earthlinknet> wrote in message
news:cja### [at] netplexaussieorg...
> In article <3f99dec8$1@news.povray.org>,
> "Cris Williams" <CLW### [at] wohrrcom> wrote:
>
> > Is there a current standard benchmark scene that is used to determine
> > parsing/rendering performance? I just upgraded my computer and would
like
> > to see how it does.
>
> benchmark.pov?
>
> (look in scenes/advanced/)
>
> --
> Christopher James Huff <cja### [at] earthlinknet>
> http://home.earthlink.net/~cjameshuff/
> POV-Ray TAG: chr### [at] tagpovrayorg
> http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Okay, using the release version of PovRay 3.5 and rendering the
benchmark.ini file that was recommended on the PovRay site this is what I
got:
----------------------------------------------------------------------------
Ray->Shape Intersection Tests Succeeded Percentage
----------------------------------------------------------------------------
Box 79358745 9334253 11.76
Cone/Cylinder 78379572 6515873 8.31
CSG Intersection 162923001 55142852 33.85
CSG Merge 741865 34312 4.63
Fractal 1831644 104482 5.70
Height Field 3901191 105560 2.71
Height Field Box 3901191 707900 18.15
Height Field Triangle 3376757 108905 3.23
Height Field Block 5889587 1742423 29.58
Height Field Cell 23435856 1852284 7.90
Isosurface 11669415 721134 6.18
Isosurface Container 12154734 11669868 96.01
Isosurface Cache 176199 42446 24.09
Mesh 12295275 64396 0.52
Plane 85284171 1281858 1.50
Sphere 260332524 153124522 58.82
Superellipsoid 620681 43704 7.04
Torus 2887283 411263 14.24
Torus Bound 2887283 480972 16.66
True Type Font 838010 80727 9.63
Clipping Object 2557372 1524945 59.63
Bounding Box 653803865 124207145 19.00
Vista Buffer 21535803 11650388 54.10
----------------------------------------------------------------------------
Isosurface roots: 11664259
Function VM calls: 169416006
----------------------------------------------------------------------------
Roots tested: 480972 eliminated: 274031
Calls to Noise: 4512422082 Calls to DNoise: 2404216638
----------------------------------------------------------------------------
Media Intervals: 36350371 Media Samples: 327887642 (9.02)
Shadow Ray Tests: 118768042 Succeeded: 48914570
Reflected Rays: 223228 Total Internal: 470
Refracted Rays: 145054
Transmitted Rays: 602889
Number of photons shot: 74025
Surface photons stored: 64488
Priority queue insert: 2226874
Priority queue remove: 163988
Gather function called: 659394
----------------------------------------------------------------------------
Smallest Alloc: 25 bytes Largest: 1440024
Peak memory used: 6401789 bytes
----------------------------------------------------------------------------
Time For Parse: 0 hours 0 minutes 2.0 seconds (2 seconds)
Time For Photon: 0 hours 0 minutes 50.0 seconds (50 seconds)
Time For Trace: 0 hours 32 minutes 31.0 seconds (1950 seconds)
Total Time: 0 hours 33 minutes 22.0 seconds (2002 seconds)
----------------------------------------------------------------------------
CPU time used: kernel 0.38 seconds, user 1984.38 seconds, total 1984.75
seconds
Render averaged 74.29 PPS over 147456 pixels
POV-Ray finished
System specs (no OCing on anything):
Asus A7N8X Deluxe Rev.2
AMD Athlon XP 3000 Barton 400Mhz FSB
1 Gig (2x512) Crucial 3200 DDR RAM
Geforce4 TI 4400
Maxtor 80GB 7200RPM 8MB HD
Win2K
"Christopher James Huff" <cja### [at] earthlinknet> wrote in message
news:cja### [at] netplexaussieorg...
> In article <3f99dec8$1@news.povray.org>,
> "Cris Williams" <CLW### [at] wohrrcom> wrote:
>
> > Is there a current standard benchmark scene that is used to determine
> > parsing/rendering performance? I just upgraded my computer and would
like
> > to see how it does.
>
> benchmark.pov?
>
> (look in scenes/advanced/)
>
> --
> Christopher James Huff <cja### [at] earthlinknet>
> http://home.earthlink.net/~cjameshuff/
> POV-Ray TAG: chr### [at] tagpovrayorg
> http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Any tips on how to improve this score besides overclocking? Would setting
the Render Priority from Normal to Highest make much difference?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Cris Williams" <CLW### [at] wohrrcom> wrote in message
news:3f99f3d5$1@news.povray.org...
> Any tips on how to improve this score besides overclocking? Would setting
> the Render Priority from Normal to Highest make much difference?
It can help a little, not a great deal though in my experience of trying
that. I think I gain a couple minutes on the benchmark.pov while using this
P4-M 2GHz notebook. My times are typically under 47 minutes.
Removing background stuff from Windows' startup list (as seen in msconfig),
keeping screensaver off, etc., and also a fresh drefragment of the disk,
seems to do well for me. Probably shouldn't be using any background services
during the benchmark. Not sure about anyone else but if I use either a low
or high GUI priority (in 'POV-Ray for Windows') I believe it bogs down.
If you haven't seen these places yet, take a look and compare.
http://www.tabsnet.com/
http://www.haveland.com/index.htm?povbench/index.php
Your system running at about 2.2GHz(?) is about the norm, just maybe a bit
slower than other people's systems. Don't rely too heavily on those though,
could be a wide variety of reasons for one being slow or fast.
--
Bob H.
http://www.3digitaleyes.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thank you for the link! Using the AMD-optimized version I got the following
(nothing else was changed):
----------------------------------------------------------------------------
Smallest Alloc: 25 bytes Largest: 1440024
Peak memory used: 6408029 bytes
----------------------------------------------------------------------------
Time For Parse: 0 hours 0 minutes 2.0 seconds (2 seconds)
Time For Photon: 0 hours 0 minutes 40.0 seconds (40 seconds)
Time For Trace: 0 hours 27 minutes 49.0 seconds (1668 seconds)
Total Time: 0 hours 28 minutes 30.0 seconds (1710 seconds)
----------------------------------------------------------------------------
CPU time used: kernel 0.27 seconds, user 1701.16 seconds, total 1701.42
seconds
Render averaged 86.67 PPS over 147456 pixel
A difference of almost 5 minutes! W00t!
Next to defrag, check msconfig, and turn off Norton antivirus (oops!).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cris Williams wrote:
> Using the AMD-optimized version I got the following
I suppose the scene is the one that is optimized for AMD-Athlon, right?
if so how a scene can be optimized for AMD-Athlon if the engine is the
same? i really don't understand that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Saul Luizaga wrote:
>
> Cris Williams wrote:
>
> > Using the AMD-optimized version I got the following
>
> I suppose the scene is the one that is optimized for AMD-Athlon, right?
> if so how a scene can be optimized for AMD-Athlon if the engine is the
> same? i really don't understand that.
No, the source code was compiled using AMD specific optimization flags.
I am not aware of any optimazations that one can do to a specific scene
file based on the CPU that is being used while maintaining identical
image results.
--
Ken Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
