Dossy Shiobara wrote:
On 2008.04.30, Rick Cobb [EMAIL PROTECTED] wrote:
Do we have any test workloads we can use to prove that and isolate the
problem down?
You have no idea how much I'd love to have someone who's overly anal
retentive--I mean, exhaustively
This isn't a very helpful response. I'm not even asking about ongoing memory
growth and overhead, at least not yet. I want to know what are the parts that
we (or at least some of us) _do_ understand and how can we at least calculate
those things so that:
1. we even have a sense of how much
Hi Titi,
I know Gustaf Neumann had a script to find application level leaks. If he
doesn't respond I can post it.
Brian
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On Behalf Of Titi Alailima
Sent: 01 May 2008 17:31
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re:
Please do - I for one would be extremely interested in seeing such script.
Thanks,
~ Alex.
On Thu, May 1, 2008 at 1:29 PM, Fenton, Brian [EMAIL PROTECTED] wrote:
Hi Titi,
I know Gustaf Neumann had a script to find application level leaks. If he
doesn't respond I can post it.
Brian
--
Dear all,
Sometime ago I made some tests on the memory leaks of
aolserver+tcs+openacs.
I'd like to share my two cents worth of what I believe I found, hoping it
might help.
Aolserver uses TCL, and TCL's got three different memory managers:
1. Standard: using the malloc, free, etc...
Let me add my 2 cents as well as i have spent a lot of time trying to
deal with ever-growing nsd process.
Currently i have nsd process (Naviserver) with size about 500Mb running
without restart for 15 days.
Tcl compiled without Zippy, with standard malloc-family. I tried it with
vtmalloc as
On 2008.05.01, Maurizio Martignano [EMAIL PROTECTED] wrote:
When using Zippy I noticed that the memory occupied by Aolserver (nsd)
always grows, without being released.
That's probably because we don't invoke madvise() anywhere. Of course,
apparently on MacOS X madvise() is broken, and on
