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 processes. but it never stops, and the tests runs all the tests and performs pretty well, each ab reports around 1000requests/sec, so I think that windows somehow lines up the processes, not making them truly concurrent, never the less, I need more hardware to run more serious tests.
Trying to run jmeter with 1000 connections is useless as jmeter takes up 88% of the CPU so Tomcat gets no cpu to handle the requests with. But I dont think it will have a problem scaling to thousands of keep alive connections. I'd like to see some other folks try out the nio connector to see if they are experiencing the same problems on windows as remy does. it would be nice to establish whether its an anomaly or the majority that would experience what he is experiencing. Filip Mladen Turk wrote: > [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 anything. >> > > Did you ever tried using 500+ concurrent connections. > With < 200 BIO is just fine on any machine with 512MB RAM. > > Try to play with larger numbers like few thousands, and > then you'll see the real stuff. > > Regards, > Mladen. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Filip Hanik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
