otismo wrote:
Thanks for checking it out, Filip.
I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
Yes, running from the trunk yields very different #s. Looking into it more,
6.0.18 didn't honor the pollerThreadCount setting.
results (all tests were run for around 3000 sa
Thanks for checking it out, Filip.
> I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
Yes, running from the trunk yields very different #s. Looking into it more,
6.0.18 didn't honor the pollerThreadCount setting.
results (all tests were run for around 3000 samples):
6.0.18:
with 2
hi Peter,
I ran your jmeter test and I get an average request time for Comet to be
13.5 seconds.
I'm running this on what will be 6.0.19, meaning 6.0.x/trunk
With a 10second timeout, you wont get timed out in exactly 10 seconds.
timeout are of absolutely lowest priority.
If there is request data
Thanks for the response, Filip. Hopefully this is more helpful...
I put a war at http://www.nomad.org/test.war containing my web app, the
source, and my jmeter test plan.
My question: why are comet timeouts getting generated substantially behind
the timeout setting?
Is it because I have incorr
peter, if you post your test code packaged in such a way that who ever
helps you doesn't have to reverse engineer your app to setup the test
case and test it locally, then you most likely wont have to pay anyone
to help you.
The more effort you provide in providing information to the list,
incl
Sorry to bump this thread. I'm willing to pay for some assistance if
anyone's interested in helping. I'm trying to figure out 2 problems
when running my system under a light-moderate load test:
1) why do my comet timeout events not get generated on time (supposed
to be every 50 seconds, averagin
I'm trying to figure out how best to configure nio so that my comet
timeout events get generated in a timely manner. I have the comet
events set to generate a timeout every 50 seconds. Works fine with
few users. Under a moderate but reasonable load the timeout gets
generated on average every 113
Thanks for the tips. Very helpful.
>> I also get the warning when trying to use keepAliveTimeout.
>> Is this property available for the nio connector?
>
> No; it's only listed under the older connector (the one labeled "Standard
> Implementation" that then somewhat ambiguously refers to HTTP).
> From: Peter Warren [mailto:tomcat.subscript...@gmail.com]
> Subject: nio connector configuration
I can't answer your real questions, but here's a bit for your minor ones.
> the acceptorThreadPriority and pollerThreadPriority are
> set using ints because I get the following warnings in the
> cat
