Netty speed bottleneck

[이희승 (Trustin Lee)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I'm skeptical about Nio.2 performance at least in Linux because there is no Real socket AIO.  You might see better numbers in other operating systems with kernel level socket AIO support.  however I have never run any performance test.  If anyone had a chance to run some test please feel free to share the result with us.

Frank, please provide some test application that exhibits your problem so that we can figure out if it's really a Netty problem or not.  If the test application is simple enough you could even compare the throughput with plain old socket version.

"Christian Migowski" <chrismfwrd at gmail.com> wrote;

>Hi,
>
>On Wed, Jan 26, 2011 at 4:02 PM, frankdurden <frank.durden at gmail.com>
>wrote:
>>
>> Hi,
>>
>> I'm testing networking speed between two blades connected via 10Gbit
>> ethernet. My test is very simple and uses Google's Protocol Buffers
>to send
>> big messages between the machines. I'm getting a speed of
>~35MBytes/sec
>> which is not that impressive. This is a memory to memory test, no
>file IO.
>> ttcp tells me that the speed should be at least 400MBytes/sec. So I'm
>> wondering where the bottleneck is, is it how I use Netty, is it Netty
>itself
>> or does it have to do with Java sockets. Can I do anything about
>this? Does
>> the 'More New I/O API' address this in anyway?
>
>Taken the information you've given us and given the fact that higher
>speeds with Netty are possible and have been seen by many people, the
>answers are:
>1. It is how you're using Netty.
>2. yes
>3. maybe
>
>regards,
>christian!
>_______________________________________________
>netty-users mailing list
>netty-users at lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/netty-users

- --
Trustin Lee, http://gleamynode.net/
Sent from a mobile device. Please excuse my brevity.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.0.8

iIkEAREIADEFAk1AR8QqHFRydXN0aW4gSGV1aXNldW5nIExlZSA8dHJ1c3RpbkBn
bWFpbC5jb20+AAoJEJb7nbIZ8zONE0oA/2s9ZCSsa+DkJ+xXi+VyXVErLqebeK91
itf5lG0H76+NAP9HibUjF+NAXAiVeVbvYw4PaSsp4A6clUBdBTJDGMUdsg==
=lZ2F
-----END PGP SIGNATURE-----