While working on a project using the NIO.2 AIO functions, I looked at the "old" NIO selector implementation and saw that the windows used the default select function, which does not scale at all on windows due to poor internal implementation. Everyone knows that on windows, IOCP is the only real solution. Of course, the callback model upon completion does not fit into the NIO selector model, but does this really mean that using NIO on windows is basically not a good idea?
For example: New AIO features include an IOCP implementation.
This is especially true when using the latest Netty environment where AIO support has been disabled. So, Netty is not working so fast on Windows, how can it be?
java selector nio netty aio
Kr0e May 21 '14 at 18:24 2014-05-21 18:24
source share