Stas Bekman wrote:
Hmm, when a new process starts it shares *everything* with the parent.
Why do you say that it's not?
It doesn't share everything with the parent. As soon as it forks there
is unshared memory, and after the first request it handles there is
usually more.
Over time, the
Perrin Harkins wrote:
Stas Bekman wrote:
Hmm, when a new process starts it shares *everything* with the parent.
Why do you say that it's not?
It doesn't share everything with the parent. As soon as it forks there
is unshared memory, and after the first request it handles there is
Stas Bekman wrote:
What you are saying is that when the server is started afresh, the newly
started child processes share more memory with the parent, than newly
started child processes some time later. Am I correct?
Yes, exactly.
Stas:
Since you wrote the script, do you recommend some good default settings in
GTopLimit to start with, i.e.,
use Apache::GTopLimit;
Apache::GTopLimit-set_max_size(1);
Apache::GTopLimit-set_min_shared_size(4000);
Apache::GTopLimit-set_max_unshared_size(6000);
$Apache::GTopLimit
Perrin Harkins wrote:
Stas Bekman wrote:
What you are saying is that when the server is started afresh, the
newly started child processes share more memory with the parent, than
newly started child processes some time later. Am I correct?
Yes, exactly.
Any ideas why?
I always do a
are only examples. pretty much each setup is unique and there
is no one-fit all setting.
use Apache::GTopLimit;
Apache::GTopLimit-set_max_size(1);
Apache::GTopLimit-set_min_shared_size(4000);
Apache::GTopLimit-set_max_unshared_size(6000);
Use Apache::VMonitor and it'll give you a good
Stas Bekman wrote:
Perrin Harkins wrote:
Stas Bekman wrote:
What you are saying is that when the server is started afresh, the
newly started child processes share more memory with the parent, than
newly started child processes some time later. Am I correct?
Yes, exactly.
Any
Perrin Harkins wrote:
Stas Bekman wrote:
Perrin Harkins wrote:
Stas Bekman wrote:
What you are saying is that when the server is started afresh, the
newly started child processes share more memory with the parent,
than newly started child processes some time later. Am I correct?
Any
Does using the Apache::GTopLimit module have the same net effect as
restarting the server itself by simply killing off the actual processes
which are growing beyond the set threshold, and thereby causing new
processes to be born?
If so, this sounds like a good alternative to setting a cron
Does using the Apache::GTopLimit module have the same net effect as
restarting the server itself by simply killing off the actual
processes
which are growing beyond the set threshold, and thereby causing new
processes to be born?
It does kill off processes that are getting too big, and you
using the Apache::GTopLimit module have the same net effect as
restarting the server itself by simply killing off the actual
processes
which are growing beyond the set threshold, and thereby causing new
processes to be born?
It does kill off processes that are getting too big, and you
So to modify my previous question, other than the loss of some shared
memory over time, GTopLimit will have the same effect as restarting
the
server?
Yes. That shared memory is important though.
On a side note, how are you tracking/discovering the this minimal loss
over
time?
Perrin Harkins wrote:
Does using the Apache::GTopLimit module have the same net effect as
restarting the server itself by simply killing off the actual
processes
which are growing beyond the set threshold, and thereby causing new
processes to be born?
It does kill off processes
The uploaded file
Apache-GTopLimit-1.02.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-GTopLimit-1.02.tar.gz
size: 5956 bytes
md5: 6c1b4bc672eab5f025eb0889cc362ad4
Changes:
* return DECLINED and not OK when not doing anything
* made the request counter
The uploaded file
Apache-GTopLimit-1.01.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-GTopLimit-1.01.tar.gz
size: 5689 bytes
md5: b2a6fc6b0ea01c6310b8e41480705486
Changes:
=head1 ver 1.01 Thu Mar 14 13:53:16 SGT 2002
* add an unshared memory threshold
::GTopLimit v1.0
The uploaded file
Apache-GTopLimit-1.0.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-GTopLimit-1.0.tar.gz
size: 5117 bytes
md5: d1847eecbf8584ae04f9c0081e22897f
=head1 ver 1.0 Wed Feb 20 11:54:23 SGT 2002
* making the DEBUG
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 8:40 PM
To: modperl list
Subject: ANNOUNCE: Apache::GTopLimit v1.0
The uploaded file
Apache-GTopLimit-1.0.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-GTopLimit-1.0.tar.gz
size: 5117 bytes
md5
The uploaded file
Apache-GTopLimit-1.0.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-GTopLimit-1.0.tar.gz
size: 5117 bytes
md5: d1847eecbf8584ae04f9c0081e22897f
=head1 ver 1.0 Wed Feb 20 11:54:23 SGT 2002
* making the DEBUG a constant variable, settable
Well, this module has been around for awhile, since mod_perl-1.22 is
distributed as a separate package. Please allow a few hours before CPAN
mirrors will get their copy before trying to download it.
The uploaded file
Apache-GTopLimit-0.01.tar.gz
has entered CPAN as
file: $CPAN/authors
19 matches
Mail list logo
