Use Netty as a backend instead of java.io for much more efficient networking.

[me4502]

Netty handles threading very well, unlike java.io sockets. Currently there is a large bottleneck in terms of single CPU performance due to usage of these old APIs.

[alejzeis]

Yes, I was thinking of using Netty, but I am not that well familiar with
it. If you could help, that would be great (on a seperate branch first).

On Wednesday, August 5, 2015, Matthew Miller notifications@github.com
wrote:

Netty handles threading very well, unlike java.io sockets. Currently
there is a large bottleneck in terms of single CPU performance due to usage
of these old APIs.

—
Reply to this email directly or view it on GitHub
#1.

[net32]

I am finishing my version of JRakLib fully using ionetty, I'll publish it here when committing, not using while (true), is in the final version already, I'm just packing up some minor bugs, performance is very good, very low CPU usage.

[net32]

@jython234 you could create a new branch, named ioNetty ? thanks

[alejzeis]

@net32 Done.

[net32]

@me4502 see: https://github.com/net32/JRakLib/tree/ioNetty

[RazvanDu]

Does the netty branch really improve performance?

[alejzeis]

I tested it and it actually appeared to be slower than master.
On Nov 29, 2015 6:17 PM, "SenanYT" notifications@github.com wrote:

Does the netty branch really improve performance?

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[me4502]

If used correctly, Netty should provide better performance.