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
[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
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.
Ah, ok.
One thing to try is building Tcl so that it doesn't use the
threaded-allocator, and to instead try
On 2006.09.30, John Buckman [EMAIL PROTECTED] wrote:
Right restarting is not something I like to doing, because most of
the time when I ctrl-c aolserver, it exists uncleanly with one of
these errors:
FYI, Berkeley DB's Tcl binding isn't truly thread-safe:
Dossy,
I still have been unable to get nsproxy to work. Did you try that thing
I sent you a few weeks back? (Basically nsproxy would work for a few
minutes and then crash the server)
Rusty
Dossy Shiobara wrote:
On 2006.09.30, John Buckman [EMAIL PROTECTED] wrote:
Right restarting is
John Buckman wrote:
Right restarting is not something I like to doing, because most of the
time when I ctrl-c aolserver, it exists uncleanly with one of these errors:
Would it work any better/more reliably to have aolserver exit itself, by
calling ns_shutdown and hopefully allowing any
