Peter Lin wrote:
Am I reading the results correctly?
tomcat 5.5.9 - 16,331.81/sec
hybrid - 7,085.54/sec
that means the hybrid connector is 2x slower. If those results are
accurate, I would say the APR connector is much better choice.
It's more complex than that.
The APR connector has a trick to optimize pipelining (where a client
would do many requests on a single connection, but with a small delay
between requests - typically, it would happen when getting lots of
images from a website). Maybe this could be added here as well. Removing
this optimization will make piepelining performance go down as well.
Note that Mladen tells me of more sendfile-like performance tricks that
can't be matched by NIO (at least for now).
Another test which could be done is comparing performance without the
"-k" setting of ab (removing the impact of any pipelining opimization,
but more of the overhead is then on the TCP stack rather than on the
connector).
I still don't like the proposed NIO solution, however, as it adds a lot
of complexity to the default thread pool (which was complex already, but
with those changes, it becomes black magic, and robustness will likely
go down). If doing NIO, I think a much simpler thread pool structure
should be used instead, like the APR endpoint does (even better, it
could be a Java 5 version taking advantage of the new thread pool APIs).
I expect Jean-Francois to live up to the hype and produce less
experimental code ;)
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
