Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
Filip Hanik - Dev Lists wrote:
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I took the liberty and added the <Executor> element to server.xml
today.
It performs surprisingly well,
I don't see why it would perform worse than your internal connector
executor :)
I was comparing to the existing stack thread pool, :)
for example, the JioEndpoint performs much better with the executor
than the worker stack, surprisingly
The results I see are average (a lot more memory, slower), but it has
far more options obviously. In particular, the default maxThreads is
way too high and blows up my poor laptop (it should be 150 IMO, like
for the current connectors).
(the j.io will not perform better or worse: with ab -k, once it gets a
thread it will never let it go away)
that's what I tested, -c 100 -k (maxThreads=10) and somehow it still
worked, and performed really well
not sure why that was, but I agree with your conclusion. for the j.io it
should simply turn off keep alives when using an executor.
Filip
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
