on my machine ab tells:
+++
Percentage of the requests served within a certain time (ms)
50% 3
66% 3
75% 3
80% 4
90% 7
95% 17
98% 40
99%176
100%919 (longest request)
+++
For NIO.
And:
+++
Percentage of the requests served within a certain time (ms
yeah, anything over 500 threads with JMeter will chew up the available CPU
cycles. tomcat needs a hardware benefactor to donate some hardware :)
peter
On 6/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
yes, I've ran 20 instances of ab (each with 50 connections) at the same
time on my wi
yes, I've ran 20 instances of ab (each with 50 connections) at the same
time on my windows box, so 1000 concurrent connections. (with tomcat's
default maxThread setting, which I think was 200)
The NIO connector handles this fine, my box is of course 100% cpu between
windows,tomcat and all the ab pr
[EMAIL PROTECTED] wrote:
I'm not seeing the windows problems, I used to have many problems on
windows using jdk1.4, but since 1.5 I have no problems at all. I do have a
brand new machine, so maybe there is some windows patch on it that I
didn't have before, other than that I can't think of anythi
7;s connector yet, but that's also my experience with
> the AJP/NIO connector: NIO is pretty much useless on Windows.
> > -Original Message-
> > From: Remy Maucherat [mailto:[EMAIL PROTECTED]
> > Sent: Monday, June 26, 2006 4:58 AM
> > To: Tomcat Developer
Bill Barker wrote:
I haven't tested Filip's connector yet, but that's also my experience with
the AJP/NIO connector: NIO is pretty much useless on Windows.
That's what I see, then, but it's not what Sun says.
Rémy
-
To unsu
t Developers List
> Subject: Re: NIO vs BIO speed
>
> Filip Hanik - Dev Lists wrote:
> > yes, I think they are looking pretty good. And I am fairly
> confident in
> > this new code, as most of it, is old tested APR code.
>
> (Of course, there hasn't been any new c
man that sucks,
I can run the same tests, even hundred thousand iterations, I get a little
worse performance than the blocking connector and a little better than the
APR connector, and it never crashes for me.
I'm in dublin at apachecon this week, but will continue as soon I get back,
have a good
Filip Hanik - Dev Lists wrote:
yes, I think they are looking pretty good. And I am fairly confident in
this new code, as most of it, is old tested APR code.
(Of course, there hasn't been any new changes, so it's not a surprise it
not working any better for me; I did reboot in the meantime, tho
https://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/tomcat/util/net/NioEndpoint.java?view=log
https://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/coyote/http11/Http11NioProcessor.java?view=log
https://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/coyote/h
I am interested in this code. Is there a way I can see the code? Thanks.
On 6/22/06, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote:
Remy Maucherat wrote:
Filip
Hanik - Dev Lists wrote:
Here is another test that I ran from a remote
machine, setting maxThreads="25" and ab concurre
Remy Maucherat wrote:
Filip
Hanik - Dev Lists wrote:
Here is another test that I ran from a remote
machine, setting maxThreads="25" and ab concurrency to 50 and keepalive
on.
In this case, NIO is a lot faster. Turn off keepalive on ab, and we get
similar results to previous run, where
Remy Maucherat wrote:
Filip Hanik
- Dev Lists wrote:
Remy, can you run your tests again, are you
still seeing a huge difference?
Obviously, you did not change anything.
yes, I changed from busy read to polling, I wasn't sure if you ran your
tests after that.
I've ran my test
Filip Hanik - Dev Lists wrote:
Here is another test that I ran from a remote machine, setting
maxThreads="25" and ab concurrency to 50 and keepalive on.
In this case, NIO is a lot faster. Turn off keepalive on ab, and we get
similar results to previous run, where BIO is a tad faster.
Scaling t
Filip Hanik - Dev Lists wrote:
Remy, can you run your tests again, are you still seeing a huge difference?
Obviously, you did not change anything.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-ma
Here is another test that I ran from a remote machine, setting
maxThreads="25" and ab concurrency to 50 and keepalive on.
In this case, NIO is a lot faster. Turn off keepalive on ab, and we get
similar results to previous run, where BIO is a tad faster.
[EMAIL PROTECTED] bin]$ ./ab -n 2 -k
16 matches
Mail list logo
