Re: [AOLSERVER] nsd and memory leaks

2004-01-10 Thread Bernd Eidenschink
On 2004.01.09, Andrew Piskorski [EMAIL PROTECTED] wrote: On Fri, Jan 09, 2004 at 12:31:39PM -0800, Jim Wilcoxson wrote: fragmentation problems - not necessarily leaks. Just restart your server once a day/week. Which is still quite frequently, and thus very conservative. From

Re: [AOLSERVER] nsd and memory leaks

2004-01-10 Thread Jim Davidson
In a message dated 1/10/04 12:03:58 AM, [EMAIL PROTECTED] writes: A dynamic content server tends to grow in our experience, and I've always assumed that's because of heap fragmentation problems - not necessarily leaks.  Just restart your server once a day/week. Yes -- memory fragementation

Re: [AOLSERVER] nsd and memory leaks

2004-01-10 Thread Jim Wilcoxson
Here's a script to dump out the memory pool info: set text set elname blocksize nfree nget nput nrequest nlock nwait foreach pel [ns_info pools] { append text \nPoolname: [lindex $pel 0]\n set i 0 foreach el [lindex $pel 1] { append text [lindex $elname $i]: $el\n

Re: [AOLSERVER] nsd and memory leaks

2004-01-10 Thread Dossy
On 2004.01.10, Jim Wilcoxson [EMAIL PROTECTED] wrote: It seems that one way to address this memory/heap problem is to force threads to exit after a certain amount of time idle, freeing their entire heap area. There is code in AS to do that, but I've never gotten it to work successfully