Calvin NG([EMAIL PROTECTED])@2001.06.06 11:31:19 +0000:
> Greetings,
>
> Correct me if I m wrong.
> For in-core web server , every copy of server loaded has the perl and/or php
> in it. For modules, its a shared library, the server is smaller size, and only
> a copy of the module is loaded in memory.
>
> However, in-core is slightly faster then modules, IIRC.
>
> I remember reading the performance pages of mod_perl, they recommend running
> mod_perl in-core servers separately as a application server.
>
> Thats my understanding of the difference between in-core and modules.
i think this is correct.
/k
>
> Regards,
> /calvin
>
> lines with :> are quotes from Mike Meyer's email
> :> Karsten W. Rohrbach <[EMAIL PROTECTED]> types:
> :> > you won't recognize it until you have to implement a heavily loaded
> :> > server with php or perl in-core. position independent code is know to be
> :> > slower, but it outperforms monolithic compiles by saving a lot of ram.
> :>
> :> Ok, where does the savings come from? You get one copy of the code,
> :> shared by all the processes running the binary, whether or not the
> :> code is in a shared library. COW for data should mean that data should
> :> be shared pretty much the same. So what have I missed?
> :>
> :> Thanx,
> :> <mike
> :> --
>
--
> In protocol design, perfection has been reached not when there is nothing
> left to add, but when there is nothing left to take away.
> --Networking truth #12, Ross Callon, RFC 1925
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.net/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- [EMAIL PROTECTED]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
PGP signature
