On Fri, 28 Feb 2003 16:06:35 -0500, Christopher James Huff
<cja### [at] earthlinknet> wrote:
> > megapov.exe +Iglowlits.pov +GAoutput.txt +W640 +H480 -A -J0.0 -FN -D
>
> glowlits.pov is not a benchmark scene, and is nothing like typical 
> scenes. I would suggest using benchmark.pov.

I was not concerned much on choosing the right sphere because I considered it as
begining for further tests with various conditions. The longer test with
benchmark.pov I leaved for weekend. Now I have results:

app.       | compiler    | GUI | P-II | PIII |
-----------+-------------+-----+------+------+
povray 3.5 | intel       | win | 2740 |  815 |
megapov    | djgpp(gcc)  | dos | 2865 |  852 |
megapov    | mingw(gcc)  | con | 2909 |  872 |
megapov    | open watcom | con | 4094 | 1234 |
megapov    | borland 5.5 | win | 4407 | 1332 |
megapov    | dmc         | con | 4907 | 1454 |

where P-II is P-II 233 MHz with

call:
  application.exe benchmark.ini +Oapp +GAoutput_app.txt -J0.0 +FN

benchmark.ini:
  -w96 -h96 +a0.3 +am1 +v -d -f -x
  +Ibenchmark.pov

P-II:
  Pentium 2 233 MHz, 128 MB, NT4 Sp 6

P-III:
  Pentium 3 730 MHz, 128 MB, Win2000

Seems time for checking profiliers.

While MinGW is in fact faster than Borland compilation it seems strange that DOS
application (DJGPP) is faster than console application. It is signifficant
difference but it can means a day for a long renderings. AFAIK they use were
build with the same GCC version and I applied the same config.h for both.

And BTW: I noticed all images produced in this test are significantly different.
I have to track differences....

ABX

Post a reply to this message