[EMAIL PROTECTED] wrote:
This morning my server complained:
unable to alloc 2169111 bytes
How large was the nsd process when it crashed?
and thus exited. So, I'm thinking that malloc fragmentation may very
well be the problem.
I read recently that the
connsperthread
parameter no longer
On Oct 2, 2006, at 11:10 PM, Nathan Folkman wrote:
[EMAIL PROTECTED] wrote:
This morning my server complained:
unable to alloc 2169111 bytes
How large was the nsd process when it crashed?
Not sure how big, I wasn't around.
But, nsd regularly grows to 2gb, and I usually shut it down around
FYI, Berkeley DB's Tcl binding isn't truly thread-safe:
http://dossy.org/archives/000307.html
I'm not using their Tcl binding, as it's not even close to thread
safe. I'm using Vlad's BerkeleyDB/aolserver nsdb driver. However,
that may be leaky, so what I was going to do is make a
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)
FYI, nsproxy worked fine for me under macosx and linux. I believe
Rusty may be running it under windows (can
On 2006.09.30, John Buckman [EMAIL PROTECTED] wrote:
What you can consider doing is using the new nsproxy module to use the
BDB Tcl binding from nstclsh in separate processes in a nsproxy pool.
Then, you're relying on BDB's concurrency (multi-process locking)
being implemented correctly.
I couldn't get it to compile under windows. Under linux, it crashes for me.
John Buckman wrote:
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)
FYI, nsproxy
This morning my server complained:
unable to alloc 2169111 bytes
and thus exited. So, I'm thinking that malloc fragmentation may very
well be the problem.
I read recently that the
connsperthread
parameter no longer works in aolserver.
I believe this parameter destroys a Tcl interpreter and
Yes, I prototyped exactly that, and it worked, and yield only a 4x
slowdown in database fetch time, rather than the 18x slowdown that
the RPC mechanism yielded. However, I probably won't initially use
that technique, as I first want to see where the bloat problem is.
Uh, if you use nsproxy to
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
On my bookmooch.com site, I'm noticing that my nsd process adds about
300mb of memory usage every day, requiring a restart once a week
after I approach my 2gb memory limit. I'm trying to fix this.
One theory I have is that the Tcl interpreters are slowly bloating.
A simple test.adp page I
Via private email, Rusty pointed me toward the connsperthread, which
does just what I need for my tcl bloating.
It's discussed at
http://www.mail-archive.com/aolserver@listserv.aol.com/msg01525.html
Can I suggest changing the default comment on the default config
file, which is currently
16 matches
Mail list logo
