It is possible. ;) There are a number of other things you can do as well to help. One example is configuring your threads such that they die and get reaped after a certain number of requests or time. This will cause memory that is currently tied up in the thread's memory pool to be returned back to the shared memory pool, which can have the net effect of lowering the overall process size.
- n On 8/7/07, Daniël Mantione <[EMAIL PROTECTED]> wrote: > > > > Op Tue, 7 Aug 2007, schreef Nathan Folkman: > > > You might also want to try running AOLserver without the Tcl threaded > > allocator (Zippy). You might want to try Hoard or if on Linux maybe give > > Google's TCMalloc a shot. Remember, the "Zippy" allocator is optimized > for > > lock avoidance, and this comes at the cost of greater memory overhead. > > Yup, I have installations where AOLserver uses very little memory. Try > this with Apache :) > > wwwrun 4552 0.0 1.4 7380 3612 ? Sl Jul26 2:21 > /opt/aolserver/bin/nsd -ft /opt/aolserver/nsd.tcl -u wwwrun > > Daniël > > > -- > 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. -- Nathan Folkman [EMAIL PROTECTED] -- 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.