+1000! Commit then review :), i've barely tested it, seems to work.., this was needed from many time ago, i've tried to use the automatic pooling capabilities, but i was stucked when trying to separate filter and extension, ;), Thanks..
Saludos , Ignacio J. Ortega > -----Mensaje original----- > De: Mladen Turk [mailto:[EMAIL PROTECTED]] > Enviado el: 6 de julio de 2002 17:27 > Para: [EMAIL PROTECTED] > Asunto: [PATCH] experimental jk2 iis thread pool > > > Hi, > > Before going to commit something I would like to hear some > opinions, and > tests preferably. > > Here are some facts: > IIS maintains a pool of threads to handle incoming HTTP > requests. When > all of these threads are in use, new requests will be > rejected. If all > the pool threads are in a wait state (for instance, running our dll), > IIS may reject incoming requests even if there is plenty of > CPU power to > handle them. > > Now since we basically most of the are waiting for a TC to > respond, the > thread pool and the patch I'm proposing effectively deals with choking > the server. > > To set the things up, you'll need to (beside the patches) put the > 'threadPool' with the value of 10 or higher in the i_r2 registry > configuration. Lesser values doesn't make sense. > > The thread pool manager currently doesn't do anything, but my > intention > is to make him a watcher for a hanged responses, and dynamic pool > allocator. The pool itself is static (defined by the threadPool > configuration value), but it will be extended with the min/max size, > closing unused connections after a peak load. > > Comments? > > MT. > ICQ# 163961212 > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
