Java Non-Blocking I/O Concepts: Difference between revisions
| Line 7: | Line 7: | ||
Until NIO, all that was available for I/O in Java were Streams (<tt>java.io.*</tt>). All operations with Streams are blocking: a thread waits until there is data to read from the Stream instance or until it can write to the Stream instance. The disadvantage of this approach is that multiple threads are required when we need to simultaneously handle multiple sources of data, such as concurrent network connections. These threads usually spend most of their time blocked waiting on I/O events. This is the I/O and threading model Tomcat is built on. Another particularity of the Stream API is that it reads or writes data one byte at a time, which is not the most efficient way of doing I/O - the O/S handle I/O in blocks. | Until NIO, all that was available for I/O in Java were Streams (<tt>java.io.*</tt>). All operations with Streams are blocking: a thread waits until there is data to read from the Stream instance or until it can write to the Stream instance. The disadvantage of this approach is that multiple threads are required when we need to simultaneously handle multiple sources of data, such as concurrent network connections. These threads usually spend most of their time blocked waiting on I/O events. This is the I/O and threading model Tomcat is built on. Another particularity of the Stream API is that it reads or writes data one byte at a time, which is not the most efficient way of doing I/O - the O/S handle I/O in blocks. | ||
NIO addresses both of this issues: it offers a method of handing I/O in an asynchronous manner, referred to as "[[#Multiplexed_Non-Blocking_I.2FO_Facility|multiplexed non-blocking I/O facility]]", described below. | NIO addresses both of this issues: it offers a method of handing I/O in an asynchronous manner, referred to as "[[#Multiplexed_Non-Blocking_I.2FO_Facility|multiplexed non-blocking I/O facility]]", described below. It also comes with APIs that allow block-oriented I/O operations, also described below. | ||
=Multiplexed Non-Blocking I/O Facility= | =Multiplexed Non-Blocking I/O Facility= | ||
Revision as of 22:11, 25 July 2018
Internal
Overview
Until NIO, all that was available for I/O in Java were Streams (java.io.*). All operations with Streams are blocking: a thread waits until there is data to read from the Stream instance or until it can write to the Stream instance. The disadvantage of this approach is that multiple threads are required when we need to simultaneously handle multiple sources of data, such as concurrent network connections. These threads usually spend most of their time blocked waiting on I/O events. This is the I/O and threading model Tomcat is built on. Another particularity of the Stream API is that it reads or writes data one byte at a time, which is not the most efficient way of doing I/O - the O/S handle I/O in blocks.
NIO addresses both of this issues: it offers a method of handing I/O in an asynchronous manner, referred to as "multiplexed non-blocking I/O facility", described below. It also comes with APIs that allow block-oriented I/O operations, also described below.
Multiplexed Non-Blocking I/O Facility
Selectors, selection keys and selectable channels work together to provide a multiplexed, non-blocking I/O facility, whose main advantage is that is much more scalable than thread-oriented blocking I/O.
The facility works as follows: a Selector instance is created using the Selector.open() static method. The Selector instance is then used to register selectable channels, so the Selector instance acts as a multiplexor of selectable channels. A selectable channel is a special type of channel that can be put into non-blocking mode, and which has to be put in blocking mode if it is to be multiplexed under a selector.
The set of channel I/O operations to be tested for readiness by the selector, also referred to as the "interest set", are also specified during the registration procedure.
The procedure returns a selection key that represents that registration.
After the registration, a selection operation can be performed to discover which channels, if any, have become ready to perform one or more of the operations in which interest was previously declared. The underlying operating system is queried for an update on registered channels' readiness. If a channel is ready, the key returned when it was registered will be added to the selector's selected-key set. The set is returned by Selector.selectedKeys(). The keys of the selected-key set can be examined to determine the operations for which each channel is ready. The key also gives access to the channel instance, which then can be used to perform the I/O operation.
java.nio.channels provides selectable channel classes corresponding to DatagramSocket, ServerSocket and Socket. If the channel needs an associated socket, the socket will be created as a side effect on this operation.
Channels cannot be deregistered directly, instead, the key representing their registration must be cancelled.
NIO (java.nio.*) offers access to underlying O/S non-blocking I/O facilities and offers a selectors mechanism through which a single thread could be notified and process I/O events arriving from multiple sources.
Also, because the underlying operating system I/O facilities are block-oriented for efficiency - hardware usually transfers data in blocks rather than byte by byte - NIO exposes block-level access via Channels and Buffers. Data can be read and written in blocks via Buffers into and from Channels. Streams only offer sequential access - once a byte has been read, it is gone from the Stream and it is the application's responsibility to cache it locally if it needs it later. With Buffer, the caching is already done, efficiently, by the O/S.
Channels are also sources of asynchronous I/O events that are routed by selectors into the application. The data transfer between Channels and Buffers is done transparently, without requiring application threads to move bytes around. An application thread is notified once the transfer had completed via an I/O event. The NIO API does not do anything that the Stream API can't do - essentially reading and writing data from/to I/O devices - but it does it faster and using less threads.
Block-access and non-blocking I/O read and write allow Java applications to implement high-speed I/O without having to write native code that would access O/S specific facilities.
Primitives
Selector
A multiplexor that allows registration of multiple selectable channels so they can be serviced by a single selector thread. The selector thread will block in select() and it will be notified by the selector's implementation only when an I/O event, such as data becoming available or a new connection being established, occurs.
Channel
Selectable channel.
ServerSocketChannel
A selectable channel used to listen for incoming network connections and create new SocketChannels for each TCP connection. The ServerSocketChannel delegates to a ServerSocket to do the actual listening.
SocketChannel
Buffer
Java NIO and TCP Connections
A working example that shows various Java NIO primitives collaborating in establishing a bidirectional TCP connection: