> > It's not mainly about memory. Memory is handled quite effieciently, cause
> > only writable pages have to be copied (on 'write-deman' only), and others
> > are shared, which actually is not unefficient. There is some overhead with
> > the fork, but this implies to _very_ heavy loads (local intranet I'd say -
> > if it's dynamic content, the load comes from other tasks, and thus doesn't
> > create that many instances) So from the memory point of view, it's not
> > that bad. (IMHO)
> OK, let's say my app uses dlls in Windows. When I start two instances of my
> apps - are those dlls loaded for each one separately or are they shared (I
> don't think so :-)
Same applies here. DLL's are just part of your application, when it runs.
It's external, to the program physically, but it gets mapped to your
applications memory space and thus makes actually no difference. Except,
that appliactions share even DLLs thus making even more memory shared, and
consume less that way. It's not only about DLLs but about any kind of
libraries.
And if some of them have even data, that are writable (internal to the
dll) then those are write-copied.
> btw: diky za vysvetleni :-)
btw: ie je zaco :)
> -pekr-
Jano
