Link Details

Link 109950 thumbnail
User 172008 avatar

By dwdyer
via paultyma.blogspot.com
Published: Sep 04 2008 / 02:27

Thousands of Threads and Blocking I/O: The Old Way to Write Java Servers Is New Again (and Way Better)
  • 12
  • 3
  • 1295
  • 507

Comments

Add your comment
User 162010 avatar

se7en replied ago:

0 votes Vote down Vote up Reply

Not quite new. Can you force close ( with immediate effect ) a stalled opened socket using the blocking api? Don't think so...
,

User 161039 avatar

mheath replied ago:

-1 votes Vote down Vote up Reply

This is old and stupid. Non-blocking NIO isn't about performance; it's about scalability.

User 172008 avatar

Dan Dyer replied ago:

0 votes Vote down Vote up Reply

The point is that, with blocking I/O, you can scale better than most people expect. So for many projects NIO is overkill. There will still be a point at which it makes sense to choose NIO, and sacrifice some throughput for increased scalability, but most projects won't reach that point.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.