Andrew Evers a écrit :Henri Gomez wrote:Also, I notice the worker are created but never released, it is normal ?
The workers are pooled. If there are a lot of workers it means that a lot of requests are being processed.
Yes, I understand that, under heavy load the number workers of is increased but they are never removed when the load fall.
For example in jakarta-tomcat-connectors, used by Tomcats, there is a Thread pool which increase to follow load but they are recycled and removed when the load decrease.
The idea will be to have :
min workers, max workers, idle workers.
You could have up to max workers, never less than min workers and ensure that there is no more than X idle workers.
Just my .1 EUR ;)
I like this idea, but don't have time to spend implementing it. Perhaps integration of another package (e.g. Jakarta Commons Pool) would make this trivial?
