Hi Igor,
that's great blog and great observations.
It could be interesting to check one more strategy here: asynchronous
write queues. Unfortunately we don't have implementation of one for
Grizzly 1.0.x.
Unlike ENBA, asynchronous write queue first tries to write buffer
immediately, and only if it's not able to write whole buffer - it
registers for async. write (using the same selector, not new one).
IMHO this approach could work better than ENBA, because, we will be
able to avoid selector/thread switches.
Thank you!
WBR,
Alexey.
On May 11, 2009, at 4:17 , Igor Minar wrote:
> I was hoping to post this sooner, but came across some *very*
> surprising results that I had to thoroughly validate - the blocking
> IO can scale!
>
> http://blog.igorminar.com/2009/05/grizzly-sendfile-and-comparison-of.html
>
> Let me know what you think, not very many people do multiplexed
> blocking IO and I think that it is an area that has a lot of
> potential and deserves more research.
>
> cheers,
> Igor
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>