 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi all,
I've been an on-again/off-again POVRay geek since '89 (???) or about that
time . I've always been interested in optimizations and specific compilers
to use to get the best results, hence I now use POVRay source to test
compilers.
Towards this end, compiling with the new MS DevStudio, using the default vc6
settings currently appears to get a 7% improvement. The Torus1.pov using
Quickres.ini at 1280x1024 [AA 0.3], results in POVRay Official 3.1g at 118
sec, VC6 build (I built) at 118 sec, and VC7 build (I built) at 110 sec.
I'm running some more tests with chess2.pov with the rendering display
turned off. If anybody is interested in my results reply, or if requested,
I post results here.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Bit late reaction though.... but I'm interested!!
"Ken Davis" <dav### [at] mediaone net> wrote in message
news:3c7ec3b1$1@news.povray.org...
> Hi all,
>
> I've been an on-again/off-again POVRay geek since '89 (???) or about that
> time . I've always been interested in optimizations and specific
compilers
> to use to get the best results, hence I now use POVRay source to test
> compilers.
>
> Towards this end, compiling with the new MS DevStudio, using the default
vc6
> settings currently appears to get a 7% improvement. The Torus1.pov using
> Quickres.ini at 1280x1024 [AA 0.3], results in POVRay Official 3.1g at 118
> sec, VC6 build (I built) at 118 sec, and VC7 build (I built) at 110 sec.
>
> I'm running some more tests with chess2.pov with the rendering display
> turned off. If anybody is interested in my results reply, or if
requested,
> I post results here.
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
