Remy Maucherat wrote:
[EMAIL PROTECTED] wrote:
Author: fhanik
Date: Wed Oct 25 15:11:10 2006
New Revision: 467787

URL: http://svn.apache.org/viewvc?view=rev&rev=467787
Log:
Documented socket properties
Added in the ability to cache bytebuffers based on number of channels or number of bytes Added in nonGC poller events to lower CPU usage during high traffic

I'm starting to get emails again, so sorry for not replying.

I am testing with the default VM settings, which basically means that excessive GC will have a very visible impact. I am testing to optimize, not to see which connector would be faster in the real world (probably neither unless testing scalability), so I think it's reasonable.

This fixes the paranormal behavior I was seeing on Windows, so the NIO connector works properly now. Great ! However, I still have NIO which is slower than java.io which is slower than APR. It's ok if some solutions are better than others on certain platforms of course.

thanks for the feedback, I'm testing with larger files now, 100k+ and also see APR->JIO->NIO NIO has a very funny CPU telemetry graph, it fluctuates way to much, so I have to find where in the code it would do this, so there is still some work to do. I'd like to see a nearly flat CPU usage when running my test, but instead the CPU goes from 20-80% up and down, up and down.

during my test
(for i in $(seq 1 100); do echo -n "$i."; ./ab -n 1000 -c 400 http://localhost:$PORT/104k.jpg 2>1 |grep "Requests per"; done)

my memory usage goes up to 40MB, then after a FullGC it goes down to 10MB again, so I wanna figure out where that comes from as well. My guess is that all that data is actually in the java.net.Socket classes, as I am seeing the same results with the JIO connector, but not with APR(cause APR allocates mem using pools) Btw, had to put in the byte[] buffer back into the InternalNioOutputBuffer.java, ByteBuffers are way to slow.

With APR, I think the connections might be lingering to long as eventually, during my test, it stop accepting connections. Usually around the 89th iteration of the test. I'm gonna keep working on this for a bit, as I think I am getting to a point with the NIO connector where it is a viable alternative.

Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to