users@grizzly.java.net

Re: Grizzly benchmarked: Enterprise Java Community: Scaling Your Java EE Applications

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Mon, 07 Jul 2008 11:34:45 -0400

Salut,

Alan Williamson wrote:
> Scott Oaks wrote:
>>> http://www.theserverside.com/tt/articles/article.tss?l=ScalingYourJavaEEApplications
>>>
>>> I guess we need to work on improving our throughput numbers :-)
>> But only for low connection counts :-)
>
> All jokeaside, i think it would be prudent to publish a good "How To"
> tuning guide for Grizzly. There are so many bells'n'whistles to turn
> that its very hard to know what to tune to get the best throughput.

Agree. I did the exercise for GlassFish v2 a while ago:

http://weblogs.java.net/blog/jfarcand/archive/2007/01/configuring_gri.html
http://weblogs.java.net/blog/jfarcand/archive/2007/03/configuring_gri_2.html

One thing I've started is to hide the complexity of embedded Grizzly Http:

http://weblogs.java.net/blog/jfarcand/archive/2008/07/extending_the_g.html

You can only configure the number of threads. All other not-so-well
designed API (lack of documentation, ugly api, etc.) are now hidden,
which will help reducing misconfiguration.

Another thing I will soon work on it to use blocking I/O for low number
of connection, and then switch to non blocking when the load increase.
That might improve throughput for low number of connection.

Still, I need to work on documentation :-)

A+

-- Jeanfrancois





>
>