Actually in my experience the sharing of memory doesn't work as well
as one would hope. While compiling perl allocates memory for code
and data (variables) from the same memory pools, so code and
variables are interlaced. Over the lifetime of a apache/mod_perl
child a lot of
On Tue, 18 Apr 2000, Stas Bekman wrote:
Let's assume that you have two different sets of scripts/code which
have a little or nothing in common at all (different modules, no base
code sharing), the basic mod_perl process before the code have been
loaded of three Mbytes and each code base
On Wed, 19 Apr 2000, Joshua Chamas wrote:
Stas Bekman wrote:
Geez, I always forget something :(
You are right. I forgot to mention that this was a scenario for the 23 Mb
of unshared memory. I just wanted to give an example. Still somehow I'm
almost sure that there are servers
On Wed, 19 Apr 2000, Gerd Knops wrote:
Stas Bekman wrote:
On Wed, 19 Apr 2000, Matt Carothers wrote:
On Tue, 18 Apr 2000, Stas Bekman wrote:
Let's assume that you have two different sets of scripts/code
which have a little or nothing in common at all (different
modules, no
My apache processes are typically 18MB-20MB in size, with all but 500K to
1MB of that shared. We restart our servers in the middle of the nite as
part of planned maintenance, of course, but even before we did that,
and even after weeks of uptime, the percentages did not change.
We do not use
At 01:44 AM 4/20/00 +0300, Stas Bekman wrote:
On Wed, 19 Apr 2000, Gerd Knops wrote:
Stas Bekman wrote:
On Wed, 19 Apr 2000, Matt Carothers wrote:
On Tue, 18 Apr 2000, Stas Bekman wrote:
Let's assume that you have two different sets of scripts/code
which have a little or
On Wed, 19 Apr 2000, Matt Carothers wrote:
On Tue, 18 Apr 2000, Stas Bekman wrote:
Let's assume that you have two different sets of scripts/code which
have a little or nothing in common at all (different modules, no base
code sharing), the basic mod_perl process before the code have been
Let's assume that you have two different sets of scripts/code which
have a little or nothing in common at all (different modules, no base
code sharing), the basic mod_perl process before the code have been
loaded of three Mbytes and each code base adds ten Mbytes when
loaded. Which makes each
It used to be one process for everything, or at least one application for
everything. Then mod_perl comes in and people have started using a tiered
system (plain server + mod_perl server). Now you're talking about
individual application servers. Someday, maybe the script will load the
server
