> 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 > > what I've heard many people don't restart their AOLservers for months. > > I tend to schedule mine to restart once a week just to be safe. > > $ ps -A -olstart,vsz,args | grep dossy.org > Sun Nov 16 00:14:54 2003 32512 /home/aolserver/bin/nsd [...] > > A month and a half without being restarted and it's only 32MB large, AND > it's using the supposedly leaky (or unpatched) version of nscgi.
# ps -A -olstart,vsz,args | grep nsd Thu Jan 30 18:19:55 2003 134064 /opt/chroot_ext/nsd [...] No need to restart it since then, as we use some ns_eval construct to reload our tcl-api-files should they change (and no nscgi, but lot's of nsv-stuff and postgres). The first few weeks I was concerned about memory leaks, as after 47 days the size of nsd was about 62 MB, two days later 76 MB, but, finally it tended to that 130MB shown above (I just found a file where I did some statistics with top). # uptime 11:11am up 388 days, 15:05, 1 user, load average: 0.00, 0.00, 0.00 ok, this particular webserver is serving only about 5500 visits/month, but I'm really very happy that AS can be so "carefree"... The only moment you can never foresee is when AS grabs twice as much memory because of its high water mark principle. But until it's not running the OS into swap space it also doesn't matter. cu Bernd. -- 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.
