|
|
|
|
|
|
| |
| |
|
|
From: Greg M Johnson
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 09:03:07
Message: <3A1A7F49.67C5DCF1@my-dejanews.com>
|
|
|
| |
| |
|
|
Can you also cite a benchmark between the new and old PC's, along with chip
type & speed, and RAM?
Jim Kress wrote:
> 1) Windows ME command line 34 sec
> 2) POV GUI 43 sec
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 12:55:11
Message: <3a1ab6ff$1@news.povray.org>
|
|
|
| |
| |
|
|
I ran it in a DOS window under Windows ME. I did not reboot to DOS.
Jim
"Geoff Wedig" <wed### [at] darwinepbicwruedu> wrote in message
news:3a1a6dec@news.povray.org...
> Matt Giwer <jul### [at] ijnet> wrote:
>
> > Jim Kress wrote:
> >>
> >> Just got a new computer with Windows ME and was trying the POV
benchmark
> >> (skyvase.pov). I ran it two ways using the Standard download of v3.1g
with
> >> the following results:
> >>
> >> 1) Windows ME command line 34 sec
> >> 2) POV GUI 43 sec
> >>
> >> Quite a large difference!
>
> > The usual answer is the difference is the overhead of running a
windows
> > OS. About 25% and a bit high but that may be the new ME. It runs so many
> > things as cycle consuming processes that you have to expect this sort of
> > thing.
>
> > Object oriented. The entire GUI screen is an object. That little
PPS
> > number in the bottom right is a daughter process. The entire screen is
> > updated for that little change. I didn't make it that way, Gates did.
>
> Was the first run in a dos window or in Dos (ie, restart computer in Dos
> only mode)? Also, was the image displaying? I've found that image
display
> takes up a large chunk of time for no reason that I can see, so I've taken
> to turning it off and only doing spot checks.
>
> Geoff
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 12:56:06
Message: <3a1ab736$1@news.povray.org>
|
|
|
| |
| |
|
|
I used the standard downloaded executable from povray.org. I did not
compile the source code.
Jim
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3a1a3d42@news.povray.org...
> Did you try with the MSVC compile of povray?
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 12:56:41
Message: <3a1ab759$1@news.povray.org>
|
|
|
| |
| |
|
|
Both runs were from the same (new) PC, one right after the other.
Jim
"Greg M. Johnson" <gre### [at] my-dejanewscom> wrote in message
news:3A1A7F49.67C5DCF1@my-dejanews.com...
> Can you also cite a benchmark between the new and old PC's, along with
chip
> type & speed, and RAM?
>
> Jim Kress wrote:
>
> > 1) Windows ME command line 34 sec
> > 2) POV GUI 43 sec
>
Post a reply to this message
|
|
| |
| |
|
|
From: Greg M Johnson
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 13:47:28
Message: <3A1AC1EF.7391EC80@my-dejanews.com>
|
|
|
| |
| |
|
|
Jim Kress wrote:
> Both runs were from the same (new) PC, one right after the other.
Yes I figured, but could you run it on your old PC and then tell us specs
for old & new PC?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 20 Nov 2000 18:34:58 -0500, Jim Kress wrote:
>Just got a new computer with Windows ME and was trying the POV benchmark
>(skyvase.pov). I ran it two ways using the Standard download of v3.1g with
>the following results:
>
>1) Windows ME command line 34 sec
>2) POV GUI 43 sec
>
>Quite a large difference!
[...]
>Anybody got any ideas why the difference was so large?
There's much happening "under the hood" in messagepassing operating systems.
Each time the statistics are updated on screen, Windows needs to do a few
messagepasses, clipping, etc.
In addition, Windows was designed to enhance visual feedback rather than
application performance.
....but OTOH, with a multitasking system, I find that raytracing _seems_ to
go faster than with a singletaksing system (In reality, it never will),
mainly because I can do other things while it's working. In addition, WinPov
will let you see a render window so you can see it something has gone wrong
with the scene.
With newer version of Windows, the overhead will just get larger. Either get
used to it, or boot "plain DOS" and render your large scenes using MS-DOS
versions.
/j
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3A1A427F.5843FFB8@ij.net>, Matt Giwer <jul### [at] ijnet>
wrote:
> Object oriented. The entire GUI screen is an object. That little PPS
> number in the bottom right is a daughter process. The entire screen is
> updated for that little change. I didn't make it that way, Gates did.
You posted another message lately blaming object-oriented programming
for large application sizes...do you have any actual data to back up
your claims? Do you even know what OOP is? I doubt it...and the more
likely explanations for large size and slow response are poor design,
the ability to more easily and quickly add features in an OOP framework,
and lack of incentive to optimize for speed and space because of
computers fast enough and with enough memory that these problems
disappear.
--
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/
<><
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 21 Nov 2000 21:36:04
Message: <3a1b3114@news.povray.org>
|
|
|
| |
| |
|
|
On my 400 MHz NT v4 SP5 machine the results are:
Command Line Box: 75 sec
From POV GUI 90 sec
"Greg M. Johnson" <gre### [at] my-dejanewscom> wrote in message
news:3A1AC1EF.7391EC80@my-dejanews.com...
> Jim Kress wrote:
>
> > Both runs were from the same (new) PC, one right after the other.
>
> Yes I figured, but could you run it on your old PC and then tell us specs
> for old & new PC?
>
Post a reply to this message
|
|
| |
| |
|
|
From: Scott Hill
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 22 Nov 2000 08:00:12
Message: <3a1bc35c@news.povray.org>
|
|
|
| |
| |
|
|
"Matt Giwer" <jul### [at] ijnet> wrote in message
news:3A1A427F.5843FFB8@ij.net...
> Jim Kress wrote:
>
> Object oriented. The entire GUI screen is an object. That little PPS
> number in the bottom right is a daughter process. The entire screen is
> updated for that little change. I didn't make it that way, Gates did.
>
Er, no, only the status bar window should update and repaint when the
PPS display changes - if that's not the case then you can't blame Mr Gates
and the author of the GUI is at fault.
--
Scott Hill.
Software Engineer.
E-Mail : sco### [at] innocentcom
PGP Key : http://pgpkeys.mit.edu:11371
Pandora's Box : http://www.pandora-software.com
*Everything in this message/post is purely IMHO and no-one-else's*
Post a reply to this message
|
|
| |
| |
|
|
From: Warp
Subject: Re: POV Benchmark Windows ME - big difference between command line and GUI
Date: 22 Nov 2000 08:47:43
Message: <3a1bce7f@news.povray.org>
|
|
|
| |
| |
|
|
Jim Kress <kre### [at] kressworkscom> wrote:
: I used the standard downloaded executable from povray.org. I did not
: compile the source code.
You don't have to. You can download the MSVC compile from povray.org.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |