I'd agree these are pretty standard features for any web-server type thing. (apache/nginx/lighttpd mod_status, tomcat's manager status page, coldfusion's cfstat, et al)
Certainly if the user is expected to tune the thread count there needs to be some sort of quantifiable method of determining an optimum value. Joe > -----Original Message----- > From: Dave Steinberg [mailto:[email protected]] > Sent: Wednesday, January 18, 2012 9:41 AM > To: [email protected] > Subject: Re: [Pound Mailing List] Pound 2.6: new threading model / log > messages > > > Even "nice to have" would be a poundctl option to show the number of > > threads currently in use (very useful for monitoring and anticipatory > > measures to avoid "thread bottle necks"). > > I like that suggestion, it would tell us the % utilization for threads, > and we could tune things from there. You could even imagine hooking > that up to a gmetric script and graphing it with ganglia to get trend > data. > > > Besides the issues described above: Wouldn't it be better to combine > > the "old" threading model (dynamic thread creation at runtime) and > the "new" > > one (fixed thread creation at startup) by using two config > directives, > > one for the number of threads created at startup and one for the > > maximum number of threads pound is allowed to create dynamically > > during runtime (like Apache does)? What do you think? > > Another good idea. > > Regards, > -- > Dave Steinberg > http://www.geekisp.com/ > http://www.steinbergcomputing.com/ > http://www.redterror.net/ > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
