memory usage in mod_perl
justdave at bugzilla.org
Wed Jan 17 01:07:41 UTC 2007
Max Kanat-Alexander wrote on 1/16/07 7:56 PM:
> On Tue, 16 Jan 2007 19:53:19 -0500 David Miller <justdave at bugzilla.org>
>> I was guessing that's probably what it was. We don't have a whole
>> lot of variables that are likely to occupy huge amounts of memory. A
>> buglist is a darn good candidate. A good start would probably be
>> undef'ing the bug object cache in our cleanup handler.
> Yeah, that is a good idea, and I'd love to do it. The problem is
> that we can't get that variable anymore--it's actually been undefined by
> perl, but perl didn't release the memory.
> Basically what I'd really love to do is force perl to release
> all unallocated memory, but I have *no* idea how to go about that.
You probably have to walk the hash and undef all the things in it. If
you just undef the hash you leave a bunch of orphaned references.
Dave Miller http://www.justdave.net/
System Administrator, Mozilla Corporation http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/
More information about the developers