Hi,
I committed a (modified) patch submitted by Dan Weinreb that makes Hunchentoot more resilient to high load conditions by limiting the number of request handler threads that can be running at any time. If you are running a site with a lot of traffic, you'll want to be aware of this change.
Documentation for this feature is not yet available.
-Hans
---------- Forwarded message ---------- From: BKNR Commits bknr@bknr.net Date: Thu, Feb 10, 2011 at 6:22 PM Subject: [bknr-cvs] hans changed trunk/thirdparty/hunchentoot/ To: bknr-cvs@common-lisp.net
Revision: 4645 Author: hans URL: http://bknr.net/trac/changeset/4645
Patch from Dan Weinreb:
limit the maximum number of request handler threads that a taskmaster may create. Support a new SOFT argument to the STOP function that makes Hunchentoot wait until all currently outstanding requests have been processed before returning.
Add a favicon.ico to the standard file tree. Refactorings in the START-OUTPUT function to separate out the actual header sending from the request processing part. The new SEND-RESPONSE function does the I/O part of sending the response header (and possibly content) and also does the logging. Used by the thread count limiting code to send a 503 message if no more threads can be created.
U trunk/thirdparty/hunchentoot/acceptor.lisp U trunk/thirdparty/hunchentoot/compat.lisp U trunk/thirdparty/hunchentoot/headers.lisp U trunk/thirdparty/hunchentoot/taskmaster.lisp U trunk/thirdparty/hunchentoot/util.lisp A trunk/thirdparty/hunchentoot/www/favicon.ico
Change set too large, please see URL above
_______________________________________________ bknr-cvs mailing list bknr-cvs@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/bknr-cvs
Great. I have a site that was having problems when it reached about 100 threads, I wonder if anybody has anecdotal data on how their hunchentoot settings behave under high load.
On Thu, Feb 10, 2011 at 12:25 PM, Hans Hübner hans.huebner@gmail.com wrote:
Hi,
I committed a (modified) patch submitted by Dan Weinreb that makes Hunchentoot more resilient to high load conditions by limiting the number of request handler threads that can be running at any time. If you are running a site with a lot of traffic, you'll want to be aware of this change.
Documentation for this feature is not yet available.
-Hans
---------- Forwarded message ---------- From: BKNR Commits bknr@bknr.net Date: Thu, Feb 10, 2011 at 6:22 PM Subject: [bknr-cvs] hans changed trunk/thirdparty/hunchentoot/ To: bknr-cvs@common-lisp.net
Revision: 4645 Author: hans URL: http://bknr.net/trac/changeset/4645
Patch from Dan Weinreb:
limit the maximum number of request handler threads that a taskmaster may create. Support a new SOFT argument to the STOP function that makes Hunchentoot wait until all currently outstanding requests have been processed before returning.
Add a favicon.ico to the standard file tree. Refactorings in the START-OUTPUT function to separate out the actual header sending from the request processing part. The new SEND-RESPONSE function does the I/O part of sending the response header (and possibly content) and also does the logging. Used by the thread count limiting code to send a 503 message if no more threads can be created.
U trunk/thirdparty/hunchentoot/acceptor.lisp U trunk/thirdparty/hunchentoot/compat.lisp U trunk/thirdparty/hunchentoot/headers.lisp U trunk/thirdparty/hunchentoot/taskmaster.lisp U trunk/thirdparty/hunchentoot/util.lisp A trunk/thirdparty/hunchentoot/www/favicon.ico
Change set too large, please see URL above
bknr-cvs mailing list bknr-cvs@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/bknr-cvs
tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
-
Hans Hübner -
Sergio Garcia