My protocol was based on LengthFieldBasedFrameDecoder. But yes, at 1K, your number looks close enough to mine that I am not worried that I am doing something wrong.<div><br></div><div>Utkarsh<br><br><div class="gmail_quote">
On Sun, Sep 13, 2009 at 8:18 AM, huican ping <span dir="ltr"><<a href="mailto:pinghuican@gmail.com">pinghuican@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The input is only 55bytes for 190,000 TPS with 100% CPU usage..<br>
For 1024bytes input, the TPS I got is 88,500 msgs/sec with 89% CPU<br>
usage. (I cannot drives up the CPU usage anymore on server machine).<br>
<br>
The code is dummy, and I was using a simple decoder inherited from<br>
FrameDecoder, and really nothing special. It is for a tcp protocol,<br>
and there is just content, and no headers. I also use default worker<br>
thread number.<br>
<br>
I don't know what your protocol is for 76K, if you need to parse<br>
headers etc, it is pretty normal.<br>
<br>
Thanks<br>
<div><div></div><div class="h5"><br>
On Sun, Sep 13, 2009 at 3:57 AM, Utkarsh Srivastava <<a href="mailto:utkarsh@gmail.com">utkarsh@gmail.com</a>> wrote:<br>
> Could you post the code? Also, what was the size of each of your messages?<br>
> On a dual core box, at 1K messages, I am only able to do 76K messages per<br>
> sec.<br>
> Thanks<br>
> Utkarsh<br>
><br>
> On Sat, Sep 12, 2009 at 9:27 PM, Huican Ping <<a href="mailto:pinghuican@gmail.com">pinghuican@gmail.com</a>> wrote:<br>
>><br>
>> Hello netty users,<br>
>><br>
>> I punched a simple netty server which decodes (FrameDecoder, checks its<br>
>> first and tailer bytes of the input) and returns message back with 55<br>
>> bytes<br>
>> input on my 2way Woodcrest machine: 2 core-2-dual at Intel(R) Xeon(R) CPU<br>
>> 5160 @3.00GHz<br>
>><br>
>> The netty server can handle more than 190,000 msgs/sec with very short<br>
>> average response time (about 0.5 ms) for persistent connection case when I<br>
>> punch the server with 100 concurrent client threads.<br>
>><br>
>> I got about 180,000 msgs/sec with about 0.28 ms avg response for<br>
>> persistent<br>
>> connection with 50 concurrent client threads.<br>
>><br>
>> The client and server are different machines. They are in the same<br>
>> sub-network, but not directly connected on the switch. So the average<br>
>> response time can be really lower than above.<br>
>><br>
>> client output:<br>
>> ==============<br>
>> |active| message | response time (ms) |avg conn|succ<br>
>> rt|<br>
>> connection |<br>
>> time(ms)|thrds | sent| succ| fail| min | avg | max<br>
>> |time(ms)|(msg/s)|pend|estb|idle|<br>
>> 10007 100 1863171 1863071 0 0.13 0.49 212.78 0.00<br>
>> 186176.78 0 100 0<br>
>> 20011 100 1901832 1901832 0 0.12 0.52 28.14 0.00<br>
>> 190126.16 0 100 0<br>
>> 30014 100 1904729 1904729 0 0.13 0.52 27.09 0.00<br>
>> 190434.81 0 100 0<br>
>> 40017 100 1901270 1901270 0 0.13 0.52 27.25 0.00<br>
>> 190069.98 0 100 0<br>
>> 50019 100 1906704 1906704 0 0.13 0.52 26.16 0.00<br>
>> 190632.27 0 100 0<br>
>> 60023 100 1906676 1906676 0 0.13 0.52 21.63 0.00<br>
>> 190610.42 0 100 0<br>
>><br>
>> It is really impressive, decent and amazing number. A big thanks goes to<br>
>> Trustin Lee for his amazing work on Netty<br>
>><br>
>> Thanks<br>
>> Huican<br>
>> --<br>
>> View this message in context:<br>
>> <a href="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" target="_blank">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</a><br>
>> Sent from the Netty User Group mailing list archive at Nabble.com.<br>
>> _______________________________________________<br>
>> netty-users mailing list<br>
>> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
><br>
><br>
> _______________________________________________<br>
> netty-users mailing list<br>
> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
><br>
><br>
<br>
_______________________________________________<br>
netty-users mailing list<br>
<a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/netty-users" target="_blank">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
</div></div></blockquote></div><br></div>