2015-12-11 23:23 GMT+01:00 Christopher Schultz <ch...@christopherschultz.net >:
> One connector to rule them all. > > Is NIO2 viable yet? The APR connector had actual blocking-reads in > situations where we wanted that. NIO on the other hand IIRC can't choose > which type of reads to do: they are always blocking. > NIO is non blocking only. NIO2 is a low level async IO framework, useful for experiments. Due to very aggressive optimizations, it performs well although it doesn't look like it would looking at the API. It should be easier to implement more complex stuff since it can easily carry around state along with the async IO operations. > > The testing that Jean-Frederic and I have done shows much higher system > resource (CPU) use for this simulated-blocking stuff. Does NIO2 perform > better? > > While I agree that CPU time is there to be used, using that CPU time in > what amounts to a spin-wait (okay, I'm overstating a bit here) isn't > satisfying. > > You can keep on talking about it, it still doesn't make any real difference anymore. The APR connector should still not be removed, it's the fastest (SSL) and it can be more reliable (or not, it depends ...). But it could be envisioned it won't be the default even if tomcat-native is present, because it's safer. Rémy
