The first 10+ revisions of NIO were terrible, but I have heard that it
has gotten much better in the last couple of years. Hopefully if
David gets NIO working we can have a "nio=true" option in the ejbd
server.
-dain
On Jul 14, 2008, at 11:23 AM, Manu George wrote:
Saw an interesting discussion regarding NIO/IO performance on linux.
If this is still valid then moving to NIO will not increase
performance on linux
http://www.theserverside.com/discussions/thread.tss?thread_id=26700
Regards
Manu
On Mon, Jul 14, 2008 at 10:53 PM, Dain Sundstrom <[EMAIL PROTECTED]>
wrote:
On Jul 13, 2008, at 6:39 PM, David Blevins wrote:
On Jul 13, 2008, at 3:13 PM, Karan Malhi wrote:
The TPS number is very impressive. If its not a complicated
setup, could
you
share some details on how I could replicate this test on my
machine. If
we
run it on our machines, then we can probably post the results of
running
on
different configurations (on our website)
Something like that would be pretty great.
http://people.apache.org/~dblevins/grinder.tar.gz
Zipped up my setup and uploaded it. You just need to tweak the
grinder.properties file. I also hacked on the bin/openejb script
a bit,
though that's not required. The grinder.py file controls the
client code,
though i don't fully understand it.
You just start things in this order:
./openejb-3.1-SNAPSHOT/bin/openejb start
./grinder-3.0.1/bin/console
./grinder-3.0.1/bin/agent
Then you click the go button on the left of the console.
Between each run you will want to restart the console. There is a
bug in
Grinder where the calculated statistics get messed up when you run
a second
time in the console (is divides TPS by 10 for each restart).
-dain
