 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Benchmark testing generaly relies on the amount of time it takes
to render a given scene. If one were to design a scene that was
parsing intensive rather than render intensive how well would it
evaluate a systems performance ?
For example I designed this scene to take exactly 30 sec. to parse
on my system. There is a camera added simply to ensure that it was
not pointed at any object and there are no lights added so that I
rendered a black screen only. Render time at 640x480 with aa = 0.3
was only 8 sec. which is inconsequential. A pigment was added to
the object to ensure that no CPU cycles were spent on sending no
pigment warnings messages to the message window for each object
created by the scene code.
camera {location < 0, 0, -3 >look_at z*-6}
#declare A = 0;
#while (A<29500)
sphere{<0,0,A>,1 pigment{rgb 1}}
#declare A=A+1;
#end
--
Wishing you Seasons Greetings and A Happy New Millennium !
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> For example I designed this scene to take exactly 30 sec. to parse
> on my system.
9.0 here... What's in your computer?
--
Homepage: http://www.faricy.net/~davidf/
___ ______________________________
| \ |_ <dav### [at] faricy net>
|_/avid |ontaine <ICQ 55354965>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Parse time of 8.0 sec. and render time of 3.0 sec. for a total of 11.0
seconds.
Pentium III 500MHz, 32KB L1 Cache, 512KB L2 Cache, 256MB 100MHz SDRAM,
13.4GB ATA66 7200RPM HardDisk.
Win98SE at 68% Resources.
Bob
"David Fontaine" <dav### [at] faricynet> wrote in message
news:386### [at] faricynet...
> > For example I designed this scene to take exactly 30 sec. to parse
> > on my system.
>
> 9.0 here... What's in your computer?
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
David Fontaine wrote:
>
> > For example I designed this scene to take exactly 30 sec. to parse
> > on my system.
>
> 9.0 here... What's in your computer?
The question right now is not how fast you can render it. We can
start a "who's computer renders the code faster" thread later once
we establish the validity of the test. Until then your parse time
vs. my parse time is meaningless.
--
Wishing you Seasons Greetings and A Happy New Millennium !
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
You need to know the specs of each computer to gauge the parsing algorithm
(I'll just go ahead and call it that anyway), don't you?
Bob
"Ken" <tyl### [at] pacbellnet> wrote in message
news:3869C7CF.F62B7EF6@pacbell.net...
>
> The question right now is not how fast you can render it. We can
> start a "who's computer renders the code faster" thread later once
> we establish the validity of the test. Until then your parse time
> vs. my parse time is meaningless.
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken <tyl### [at] pacbellnet> wrote:
: which is inconsequential.
What does this mean?
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If you're asking what the word is, it's meaning as the AOL online dictionary
has it is:
in*con*se*quen*tial (adjective)
First appeared 1621
1 a : ILLOGICAL
b : IRRELEVANT
2 : of no significance : UNIMPORTANT
-- in*con*se*quen*ti*al*i*ty (noun)
-- in*con*se*quen*tial*ly (adverb)
If not asking the definition, then I guess Ken will have to reply to any
other meaning.
Bob
"Nieminen Juha" <war### [at] punarastascstutfi> wrote in message
news:3869e319@news.povray.org...
> Ken <tyl### [at] pacbellnet> wrote:
> : which is inconsequential.
>
> What does this mean?
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
And POV-Ray for Windows v3.1g. Don't know how I could have left that most
vital part out.
Bob
"omniVERSE" <inv### [at] aolcom> wrote in message
news:3869a854@news.povray.org...
> Parse time of 8.0 sec. and render time of 3.0 sec. for a total of 11.0
> seconds.
> Pentium III 500MHz, 32KB L1 Cache, 512KB L2 Cache, 256MB 100MHz SDRAM,
> 13.4GB ATA66 7200RPM HardDisk.
> Win98SE at 68% Resources.
>
> Bob
>
> "David Fontaine" <dav### [at] faricynet> wrote in message
> news:386### [at] faricynet...
> > > For example I designed this scene to take exactly 30 sec. to parse
> > > on my system.
> >
> > 9.0 here... What's in your computer?
> >
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I was asking for both the meaning of the word and what Ken meant with
it.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <38698759.90BDCD6B@pacbell.net>, lin### [at] povrayorg
wrote:
> Benchmark testing generaly relies on the amount of time it takes
> to render a given scene. If one were to design a scene that was
> parsing intensive rather than render intensive how well would it
> evaluate a systems performance ?
>
> For example I designed this scene to take exactly 30 sec. to parse
> on my system. There is a camera added simply to ensure that it was
> not pointed at any object and there are no lights added so that I
> rendered a black screen only. Render time at 640x480 with aa = 0.3
> was only 8 sec. which is inconsequential. A pigment was added to
> the object to ensure that no CPU cycles were spent on sending no
> pigment warnings messages to the message window for each object
> created by the scene code.
>
> camera {location < 0, 0, -3 >look_at z*-6}
>
> #declare A = 0;
> #while (A<29500)
> sphere{<0,0,A>,1 pigment{rgb 1}}
> #declare A=A+1;
> #end
With the official 3.1g.r2, cache set to maximum:
Time For Parse: 0 hours 0 minutes 13.0 seconds (13 seconds)
Time For Trace: 0 hours 0 minutes 8.0 seconds (8 seconds)
Total Time: 0 hours 0 minutes 21.0 seconds (21 seconds)
With MacMegaPOV:
Time For Parse: 0 hours 0 minutes 14.0 seconds (14 seconds)
Time For Trace: 0 hours 0 minutes 1.0 seconds (1 seconds)
Total Time: 0 hours 0 minutes 15.0 seconds (15 seconds)
My computer is a Power Macintosh G3 266 "beige" desktop, with 96MB RAM,
booting from an external SCSI 9.1GB LaCie hard drive. The OS I ran these
tests under is Mac OS 8.6(I haven't gotten Mac OS 9 yet, and have been
too busy to do anything with LinuxPPC).
I would suggest a scene file that does some more complex calculations
instead of just creating a bunch of objects.
--
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
