users@grizzly.java.net

Proxy implementation

From: Karsten Ohme <widerstand_at_t-online.de>
Date: Tue, 5 Jun 2007 14:14:47 +0200

Hi,

The main problem of implementation was the usage of Context. I thought
Context can be used to store global attributes, but this seem not to be
true, everything is setup again for each SelectionKey event. I have
attached teh implementation. It get sometimes a
ClosedConnectionException, don't know who closed it, but the most time
it works.
The performance of my implementation is quite poor.
Using Callbacks and TCPConnector seems to be cumbersome and not working.
I don't believe this can boost the performance.
Can have used a blocking connect method and write the dat in blocking
mode. Can this cause problems? As far as I see the Pipiline is executed
eahc time a SelectionKey event happens but by defualt 20 threads are
only executed. Can this be a limit? Can the performance be improved?

I have also attached test results from JMeter compared to a blocking
solution and a direct conenction to a Tomcat server.

Ragards,
Karsten




grizzlyPerformance.png
(image/png attachment: grizzlyPerformance.png)