[EMAIL PROTECTED] wrote:
So did setting connsperthread take care of the bloating? I keep
seeing assertions that memory use by AOLserver should level off at
some steady state - perhaps controlled by this parameter. But I have
yet to see any one come back and say "I changed X to Y and now my
server doesn't behave like it has a memory leak".
FYI, BookMooch.com bloats to 2gigs within 4 days of use and needs to
be restarted.
I'm hoping that the problem is with the berkeleydb driver AOLserver
driver, and am going to dry another database connectivity technique
(RMI) to see if that fixes it. If not...
-john
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to
<[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the
Subject: field of your email blank.
Your problem is most likely the Tcl memory allocator, and fragmentation
that can occur within the pools. There have been some posts detailing
these issues a few months ago I think.
One thing to try is building Tcl so that it doesn't use the
threaded-allocator, and to instead try something like Hoard or Google's
tcmalloc. Now all that aside, is it really a big deal to do rolling
restarts?
- n
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
