[xSocket-develop] Performance issue
Status: Inactive
Brought to you by:
grro
|
From: Betten, T. <tho...@op...> - 2009-02-24 16:57:01
|
Dear mailing list,
I've written an AJP server using xSocket v2.4.3 library since I read many articles
stating that NIO is a must-have to build a high-performance and scalable web application.
So I started to implement an alternative to my common thread-per-socket approach, but
the test results (using JMeter) showed that the xSocket implementation is slower than
the old approach.
Is this a "normal" behavior? Meaning "Of course your application is slower, but more
scalable and robust regarding many, many socket connections"
I guess I'm using wrong or even missing necessary tuning parameters, but the performace
section in the online documentation does not give me a hint. Currently server runs in
SYNC mode.
Here's a list of options/properties I use:
- On server creation:
sysprops.put("org.xsocket.connection.server.readbuffer.usedirect", "true");
- onConnect():
connection.setAutoflush(false);
connection.setOption(INonBlockingConnection.TCP_NODELAY, "true");
Is the ASYNC flush-mode generally preferable to SYNC mode?
What is an appropriate value for write transfer rate if package size is limited to 8192 bytes?
Are there any other tuning options that I am missing?
Any help would be appreciated...
--
Thorben Betten
|