190,000 msgs/sec with very short avg response time (about 0.5 ms) for persistent connection case when I punch with only 100 concurrent client threads.

[Huican Ping]

Hello netty users,

I punched a simple netty server which decodes (FrameDecoder, checks its
first and tailer bytes of the input) and returns message back with 55 bytes
input on my 2way Woodcrest machine: 2 core-2-dual at Intel(R) Xeon(R) CPU
5160 @3.00GHz

The netty server can handle more than 190,000 msgs/sec with very short
average response time (about 0.5 ms) for persistent connection case when I
punch the server with 100 concurrent client threads.

I got about 180,000 msgs/sec with about 0.28 ms avg response for persistent
connection with 50 concurrent client threads.

The client and server are different machines. They are in the same
sub-network, but not directly connected on the switch. So the average
response time can be really lower than above.

client output:
==============
        |active|     message     |   response time (ms)   |avg conn|succ rt| 
connection  |
 time(ms)|thrds | sent| succ| fail|  min  |   avg  |  max 
|time(ms)|(msg/s)|pend|estb|idle|
    10007    100 1863171 1863071     0    0.13     0.49  212.78     0.00
186176.78    0  100    0
    20011    100 1901832 1901832     0    0.12     0.52   28.14     0.00
190126.16    0  100    0
    30014    100 1904729 1904729     0    0.13     0.52   27.09     0.00
190434.81    0  100    0
    40017    100 1901270 1901270     0    0.13     0.52   27.25     0.00
190069.98    0  100    0
    50019    100 1906704 1906704     0    0.13     0.52   26.16     0.00
190632.27    0  100    0
    60023    100 1906676 1906676     0    0.13     0.52   21.63     0.00
190610.42    0  100    0
    
It is really impressive, decent and amazing number. A big thanks goes to
Trustin Lee for his amazing work on Netty

Thanks
Huican 
-- 
View this message in context: http://n2.nabble.com/190-000-msgs-sec-with-very-short-avg-response-time-about-0-5-ms-for-persistent-connection-case-when--tp3635215p3635215.html
Sent from the Netty User Group mailing list archive at Nabble.com.