> Im curious why you dont just set minthreads = maxthreads at startup to reduce load.
Because a) I don't know what a good value is for maxthreads, so overestimate it; b) It will take longer to get the server to accept requests when starting up. <BR> </P></DIV>>This server does not accumulate any data in ns_shares, so I'm trying > <DIV></DIV>>to figure out if this 45MB memory growth is reasonable for adding 6 > <DIV></DIV>>additional threads. It doesn't seem reasonable. Anyone have > <DIV></DIV>>suggestions for tracking down what's happening? > <DIV></DIV> > <P>Remember that the 6 threads may not represent all threads that have been >started/died off. If like you said in previous post you have maxthreads = ~ 40 then 2 >MB per thread does not seem unreasonable to me for a production server. Remember also >that once allocated that memory may be later reused in the zippy alloc method. So >even if your memory is showing 85 MB that may be what peak was but may not grow much >larger if peak activity has been hit.</P> We're not using detached threads and I didn't have threadtimeout set (do now though), so I think no threads have died. We are using exec on this server, regular allocator, and TCL 7.6. I remember something a while back about exec leaks? Guess the real test will be whether we still need to restart the server every day. The good news is, it hasn't crashed yet like 2.3.3 was doing! Jim
