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.
