Alan Williamson wrote:
> mmmm then that doesn't bode well for Grizzly does it?
>
> that suggests Grizzly cannot handle high volumes without an artifical
> throttle infront of it. I won't believe that! I have faith in the
> Grizzly!!! ;)
LOL..no it means Grizzly is not configured properly, so it fail in some
sense (if it fail :-)). Can you set DefaultPipeline.setMaxQueueSize(-1)?
I suspect that might be the problem....
Let me send you a patch that have some configuration already done to see
if that help. Just need to compile it.
A+
-- Jeanfrancois
>
> besides, i don't think 110 requests per second is that fast, surely you
> have had it working harder than that in your tests?
>
>
> Jeanfrancois Arcand wrote:
>>> am not sure what you mean? nginx is sending *all* requests to Grizzly.
>>
>> There is probably a delay nginx introduce when proxing Grizzly, hence
>> all the requests don't necessary hit Grizzly at the same time (some
>> throttling). I suspect that might explain why...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>