I took a quick look and didn't see anything that stuck out like a sore
thumb. I was hoping to maybe catch a background thread that was
misbehaving or something... It also seems to me that to be really
useful, one would need to capture and graph some of those memory stats
over time. That would probably help you to get a better picture as to
exactly when the growth is occurring, and where.

You could do this pretty easily by having a scheduled proc that would
periodically dump the results of "ns_info pools" to a file, which you
could then graph. Hopefully the example stats page code I posted a
couple of days ago provides enough documentation in the code as to
exactly what "ns_info pools" returns. If it doesn't let me know.

At this point it seems like your efforts might be better spent working
with Dossy to get one of the profiling tools to work correctly with
AOLserver.

- n


On Jan 28, 2005, at 10:14 PM, Janine Sisk wrote:

On Jan 28, 2005, at 3:52 PM, Nathan Folkman wrote:

As promised, below is slightly cleaner version (still needs more work)
that ties in some of the information from "ns_info threads". Hopefully
this will help a little.

Ok, I've posted this at http://www.furfly.net/janine/memory-pools.html (replaces the old one).

I can see what you did (split up the data by thread) and it makes
sense, but I still don't really know what to make of these numbers, or
how I can get from here to figuring out what's consuming all the
memory.

A couple of days ago I tried to run nsd with valgrind, but it didn't
seem to work.  The only output I got was from a few threads that had
exited during startup;  it seemed like valgrind wasn't able to handle
the child processes spawned by the initial thread.  I think they must
have changed valgrind recently, because the version I have (freshly
downloaded) requires the --tool parameter, which Dossy didn't use when
he posted his valgrind runs a week or so ago.

Thanks for your help, Nathan!

janine


-- 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.



--
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.

Reply via email to