> > >[Dossy] > > > 40-60MB is nothing. I'd worry if your nsd grows beyond 2GB. > > > > Doing what? > > Just about anything. If your stacksize is set to, say, 1 MB ... and > you've got 20 threads for handling connections, you're looking at a nsd > footprint of at least 20 MB. 40-60 MB is very reasonable for a site of > any non-trivial amount of traffic.
Okay, that sounds reasonable, but 2GB? What kind of work load would drive an nsd process up into the gigabytes of memory usage? > > This particular machine only has a 512mb of ram, and serves mostly > > static content. I have bigger plans for it though. > > Look at the nsd.tcl config. ... see what different settings are set to. > It's very believable that an out-of-the-box config would produce an nsd > in the 40-60 MB ballpark. That would be tolerable on a fairly loaded site, doing goodly amounts of database stuff and such. The site I am testing my first production AOLserver on is only doing mild static stuff with a few light cgi calls. I wondered where (if) it was going to stop growing. The way it was creeping looked suspiciously like a leak to me, which appears to have been confirmed by Scott. (I rebuilt with 'Ns_DStringInit(&dsPtr);' banged out of nscgi.c, and have been running it for four hours. It's sitting, apparently stable, at 14.5mb now.) -- 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.
