Salut,
glassfish_at_javadesktop.org wrote:
> Hi Jeanfrancois
Sorry for the delay...
>
> Thanks for your reply. I don't have a thread dump handy right now. However while discussing with a colleague, we came around discussing a particular functionality of ours which is synchronised. Not sure if this is causing the increase on load under the Grizzly thread model. Does that make any sense?
Maybe this synchronize are producing a dead lock...it is hard to say.
>
> I was expecting more than 5 busy threads to show up, but still puzzles as to why we have a low number. Perhaps the above synchronisation has some effect(?).
Maybe...but if no more threads are created it is because Grizzly is able
to server the load with only 5 threads.
>
> As for the machine spec, we are running with 8 cores. I was going to bump up the Acceptor threads to 8 initially, but thought would start with 5 to see how it works out. My next test would be to increase it to 8 though. Would you be able to shed some light on the benefits, beyond that fact that it has more threads to work with.
It's more how connection get accepted with the acceptor-threads. The
real number of thread is configurable using the <request-procesor ..>
element in domain.xml.
>
> As ever thanks very much and look forward for your comments.
>
A+
-- Jeanfrancois
> Cheers
> -- Imran
> [Message sent by forum member 'imranbohoran' (imranbohoran_at_gmail.com)]
>
> http://forums.java.net/jive/thread.jspa?messageID=367957
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>