The advantage of using NIO versus BIO in a berth?

Question

The advantage of using NIO versus BIO in a berth?

Any compromise experience regarding nio vs bio when working with heap and computationally intensive process for each request with execution time in the range (100 ms-900 ms)?

+3

java jetty nio

recycle Dec 27 '08 at 17:34

source share

3 answers

RogerV · Answer 1 · 2008-12-28T07:52:54+0000

The real problem is how many concurrent open connections you want to scale for each physical server (say, to support push ala Comet pattern messaging with the server - and who doesn't want to do this these days?), NIO will provide you with realism ranging from 10,000 to 20,000. Streams are an extremely expensive resource in terms of OS implementation (for thread memory consumption and overhead for context switching). Thus, thousands of NIO connections can be supported using a modest thread pool.

Use an NIO infrastructure like MINA, and rolling out NIO is not bad at all. (This is actually quite simple.) I rolled up my own NIO and then turned on MINA. MINA is a good way to go.

http://mina.apache.org/testimonials.html