And also this:
"NDB is an in-memory storage engine"
No longer true: As of MySQL 5.1.6 it's possible to store
tables on disk rather than in memory.
See http://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-disk-data.html
But, I wouldn't recommend using MySQL cluster to power your
high traffic we
my $callback = ModPerl::Util::current_callback();
For a PerlOutputFilterHandler the current_callback() function returns
"PerlResponseHandler".
That sounds like a bug, or am I doing something wrong ?
Server: Apache/2.0.54 (FreeBSD 6.0) mod_ssl/2.0.54 OpenSSL/0.9.7g
mod_apreq2-20050712/2.1.
Exactly what I was look for ! Thanks !
- Original Message -
From: "Geoffrey Young" <[EMAIL PROTECTED]>
To: "Len Kranendonk" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, February 01, 2006 3:32 PM
Subject: Re: What handler am I ?
Len Kranendonk wrote:
Hello all,
Suppose I have this:
PerlModule My::Module
PerlChildInitHandler My::Module
PerlOutputFilterHandler My::Module
In the sub handler {} , is there a way to
determinate what type of handler I am supposed to be ?
I'm running mod_perl2 for that
matters.
Len
So, how
come it is growing, and more importantly, how can
I control it ?
BTW: I have this problem on all our FreeBSD boxes
running different applications.
Is FreeBSD / mod_perl just a bad combo
?
Len Kranendonk
I found it !!!
Issueing an "apachectl restart" (or kill -HUP) make the apache parent
process size grow !
This is the case on all of our FreeBSD boxes. I can't reproduce it on Linux.
Take a look at this:
apachectl start
# ps
This doesn't really help you, but I don't notice the parent growing on
any of my FreeBSD boxes doing a variety of things.
So, most likely I'm doing something that you don't do
Are you using ModPerl::Registry, because I still do.
Are you using IPC::SharedCache for your HTML::Template caching?
No, I'm using the "file_cache=>1" option, which uses Storable (I believe).
How are you measuring this?
top, or ps aux and watch the RSS column (the real memory (resident set)
size of the process (in 1024 byte units)).
A sample top output:
PID USERNAME PRI NICE SIZERES STATETIME WCPUCPU COMMAND
87075 www40 178M 174M accept 0:32 3.
Do you have any globals or other shared information that grows very
large? Do you read in any large data sets either from a database or
a file into the application all at once?
We're using a global %session hash, which is undef 'fed when the session is
closed.
I'm not reading in large data
he children. So, how
come it is growing, and more importantly, how can
I control it ?
BTW: I have this problem on all our FreeBSD boxes
running different applications.
Is FreeBSD / mod_perl just a bad combo
?
Len
Kranendonk
> Are they always in Storable::thaw? What are you thawing?
No, it happens on any module:
Out of memory during request for 55504 bytes, total sbrk() is 26630144
bytes!
[Fri Dec 2 11:24:11 2005] TagFilter.pm: Callback called exit at
/knvb/WebGUI/li
b/HTML/TagFilter.pm line 402.
[Fri Dec 2 11:24:
Hello all,
Once in a while I get "Out of memory" errors on our mod_perl servers. They
look like this:
Out of memory during request for 77000 bytes, total sbrk() is 14952448
bytes!
[Mon Nov 7 00:08:01 2005] thaw.al): Callback called exit at
../../lib/Storable.pm (autosplit into ../../lib/auto/Sto
> trunks# apachectl start
> Segmentation fault (core dumped)
>
> Of course, the FreeBSD pkg builds are without debugging.
> I'll give that a whirl shortly.
Thanks for that Philip. I know perl but this is way beyond my reach.
> Somewhere, it uses $& or one of those operators that change the regex
engine of
> perl. I don't know if its been fixed in 5.8.7 or maint.
I'm running 5.8.7 and it still has this problem.
I'm currently working around it by not preloading Image::Magick and using
"require"
to load Image::Magick o
> I'm going to have to eat part/all of my words here as there is no port for
> p5-Image-Magick.
There is a port ImageMagick which also contains the perl module
Image::Magick.
I've mailed the maintainer. Not sure though if he would be able to fix it as
he might
not be into perl.
As soon as I preload Image::Magick under mod_perl2
on FreeBSD (5.3, 5.4 and 6.0) I
get a "Segmentation fault (core dumped)" when
I start Apache.
Without preloading it works fine.
What's the best place to report this bug ?
17 matches
Mail list logo
