 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <slr### [at] teal hhjpat> ,
hjp### [at] SiKituwsracat (Peter J. Holzer) wrote:
> The code segment of povray for linux/intel is about 550 kB. Following
> the rule of thumb that 90 percent of the time is spent in 10 % of the
> code, a dll with the time critical routines would be about 55 kB. So for
> each supported processor variant the executable package would increase
> by about 55 kB.
pvengine.exe (at least the VC 6 one) is 1622016 bytes. On the Mac you get
about the same size.
> Of course this assumes that the time critical routines can be moved to a
> dll. It is possible that these code fragments are so short that function
> calls (as opposed to inlining) add more overhead than can be saved by
> carefully hand-crafting them in assembler.
The question is how much overhead does calling DLL function introduce? At
least on Macs a shared library call is done by addressing the function via a
table. In total about 10 instructions. For simple operations this would
eliminate the benefit. Plus, vector and color math are not done with
functions in POV-Ray (they are C macros). This benefit together with the
compiler optimisations that come along with it would be lost.
> I am also ignoring the trouble of generating and loading dlls on
> different platforms since these optimizations are platform dependent
> anyway.
True.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote in message <3a78cef2$1@news.povray.org>...
>pvengine.exe (at least the VC 6 one) is 1622016 bytes. On the Mac you get
>about the same size.
That includes some rather huge bitmap images. Eliminate those, and you have
a much smaller executable.
--
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ken wrote:
> And thus the reason Chris Cason offers two compiles for Windows. One with
> Watcom the other MSVC6++ both pentium II optimized. The price of each of
> these two compilers is not cheap and requires that the developer has access
> to equipment with archetecture the compiler is optimized for.
I beg your pardon, but there's only one official version for windows (at least on
povray.org). If there is a faster compile available, I'd like to hear of it.
...Chambers
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hmm... I think everyone is starting (?) to go about this the wrong way... Myself
included...
Ok, what not simply keep the official version the way it is, and _somebody_
offer a platform specific, _unofficial_ compile? I know someone recently did a
3dNow version (sorry, I don't remember who), this would be greatly appreciated
if you can find a good way of posting it on the web...
...Chambers
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ben Chambers wrote:
> I beg your pardon,
You are pardoned :)
> but there's only one official version for windows (at least on
> povray.org). If there is a faster compile available, I'd like to hear of it.
The official distribution has the Watcom compile. There is an official
MSVC6++ compile also available that my personal testing shows a reasonable
perfomance increase (see my comparison testing report in the announcements
group). You can download the MSVC6++ version directly from the link provided
below.
ftp://povray.org/pub/povray/Official/Windows/pve-vc6.zip
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ben Chambers wrote:
>
> Hmm... I think everyone is starting (?) to go about this the wrong way... Myself
> included...
> Ok, what not simply keep the official version the way it is, and _somebody_
> offer a platform specific, _unofficial_ compile? I know someone recently did a
> 3dNow version (sorry, I don't remember who), this would be greatly appreciated
> if you can find a good way of posting it on the web...
Historically this is the way it has been handled. There have been
many patches released using various compilers and optimizing routines
over the years. Some work better than others and it takes the pressure
off of the POV-Team from having to purchase additional software and
hardware. It also minimizes their support headaches (to a certain
degree).
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mark Wagner wrote in message <3a78ee3f@news.povray.org>...
> Thorsten Froehlich wrote in message <3a78cef2$1@news.povray.org>...
> >pvengine.exe (at least the VC 6 one) is 1622016 bytes. On the Mac you get
> >about the same size.
>
> That includes some rather huge bitmap images. Eliminate those, and you have
> a much smaller executable.
dos version of megapov06a compiled with djgpp is about 1.2 MB
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Peter J. Holzer <hjp### [at] sikituwsracat> wrote:
: a dll with the time critical routines
What do you mean "a dll"?
How do you use dll's with *STANDARD* C (or C++)?
Don't forget that povray has to be compiled for several platforms. Also
for Linux (I don't think that Linux supports Windows DLL's), not to talk
about other platforms as well (several Unix variants, MacOS, DOS, BeOS, etc).
--
char*i="b[7FK@`3NB6>B:b3O6>:B:b3O6><`3:;8:6f733:>::b?7B>:>^B>C73;S1";
main(_,c,m){for(m=32;c=*i++-49;c&m?puts(""):m)for(_=(
c/4)&7;putchar(m),_--?m:(_=(1<<(c&3))-1,(m^=3)&3););} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Has anyone considered support for multiprocessor systems ?
ie multithreaded POV ...
I can get som free time on a quad Xeon System, but it would be wasted on
pov.
Joe ...
"Wlodzimierz ABX Skiba" <abx### [at] abxartpl> wrote in message
news:3a7919fd$1@news.povray.org...
> Mark Wagner wrote in message <3a78ee3f@news.povray.org>...
> > Thorsten Froehlich wrote in message <3a78cef2$1@news.povray.org>...
> > >pvengine.exe (at least the VC 6 one) is 1622016 bytes. On the Mac you
get
> > >about the same size.
> >
> > That includes some rather huge bitmap images. Eliminate those, and you
have
> > a much smaller executable.
>
>
> dos version of megapov06a compiled with djgpp is about 1.2 MB
>
> ABX
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nikole & Joe Arcaro wrote:
>
> Has anyone considered support for multiprocessor systems ?
>
> ie multithreaded POV ...
http://www.wozzeck.net/images/pmp/
Bouf.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
