Scalable IO in Java网络
http://gee.cs.oswego.edu/dl/cpjslides/nio.pdf多线程
基本上全部的网络处理程序都有如下基本的处理过程:
Read request
Decode request
Process service
Encode reply
Send reply异步
Classic Service Designs
socket
简单的代码实现:ide
class Server implements Runnable { public void run() { try { ServerSocket ss = new ServerSocket(PORT); while (!Thread.interrupted()) new Thread(new Handler(ss.accept())).start(); //建立新线程来handle // or, single-threaded, or a thread pool } catch (IOException ex) { /* ... */ } } static class Handler implements Runnable { final Socket socket; Handler(Socket s) { socket = s; } public void run() { try { byte[] input = new byte[MAX_INPUT]; socket.getInputStream().read(input); byte[] output = process(input); socket.getOutputStream().write(output); } catch (IOException ex) { /* ... */ } } private byte[] process(byte[] cmd) { /* ... */ } } }
对于每个请求都分发给一个线程,每一个线程中都独自处理上面的流程。性能
这种模型因为IO在阻塞时会一直等待,所以在用户负载增长时,性能降低的很是快。this
server致使阻塞的缘由:spa
一、serversocket的accept方法,阻塞等待client链接,直到client链接成功。线程
二、线程从socket inputstream读入数据,会进入阻塞状态,直到所有数据读完。设计
三、线程向socket outputstream写入数据,会阻塞直到所有数据写完。
client致使阻塞的缘由:
一、client创建链接时会阻塞,直到链接成功。
二、线程从socket输入流读入数据,若是没有足够数据读完会进入阻塞状态,直到有数据或者读到输入流末尾。
三、线程从socket输出流写入数据,直到输出全部数据。
四、socket.setsolinger()设置socket的延迟时间,当socket关闭时,会进入阻塞状态,直到所有数据都发送完或者超时。
改进:采用基于事件驱动的设计,当有事件触发时,才会调用处理器进行数据处理。
Basic Reactor Design
代码实现:
class Reactor implements Runnable { final Selector selector; final ServerSocketChannel serverSocket; Reactor(int port) throws IOException { //Reactor初始化 selector = Selector.open(); serverSocket = ServerSocketChannel.open(); serverSocket.socket().bind(new InetSocketAddress(port)); serverSocket.configureBlocking(false); //非阻塞 SelectionKey sk = serverSocket.register(selector, SelectionKey.OP_ACCEPT); //分步处理,第一步,接收accept事件 sk.attach(new Acceptor()); //attach callback object, Acceptor } public void run() { try { while (!Thread.interrupted()) { selector.select(); Set selected = selector.selectedKeys(); Iterator it = selected.iterator(); while (it.hasNext()) dispatch((SelectionKey)(it.next()); //Reactor负责dispatch收到的事件 selected.clear(); } } catch (IOException ex) { /* ... */ } } void dispatch(SelectionKey k) { Runnable r = (Runnable)(k.attachment()); //调用以前注册的callback对象 if (r != null) r.run(); } class Acceptor implements Runnable { // inner public void run() { try { SocketChannel c = serverSocket.accept(); if (c != null) new Handler(selector, c); } catch(IOException ex) { /* ... */ } } } } final class Handler implements Runnable { final SocketChannel socket; final SelectionKey sk; ByteBuffer input = ByteBuffer.allocate(MAXIN); ByteBuffer output = ByteBuffer.allocate(MAXOUT); static final int READING = 0, SENDING = 1; int state = READING; Handler(Selector sel, SocketChannel c) throws IOException { socket = c; c.configureBlocking(false); // Optionally try first read now sk = socket.register(sel, 0); sk.attach(this); //将Handler做为callback对象 sk.interestOps(SelectionKey.OP_READ); //第二步,接收Read事件 sel.wakeup(); } boolean inputIsComplete() { /* ... */ } boolean outputIsComplete() { /* ... */ } void process() { /* ... */ } public void run() { try { if (state == READING) read(); else if (state == SENDING) send(); } catch (IOException ex) { /* ... */ } } void read() throws IOException { socket.read(input); if (inputIsComplete()) { process(); state = SENDING; // Normally also do first write now sk.interestOps(SelectionKey.OP_WRITE); //第三步,接收write事件 } } void send() throws IOException { socket.write(output); if (outputIsComplete()) sk.cancel(); //write完就结束了, 关闭select key } } //上面 的实现用Handler来同时处理Read和Write事件, 因此里面出现状态判断 //咱们能够用State-Object pattern来更优雅的实现 class Handler { // ... public void run() { // initial state is reader socket.read(input); if (inputIsComplete()) { process(); sk.attach(new Sender()); //状态迁移, Read后变成write, 用Sender做为新的callback对象 sk.interest(SelectionKey.OP_WRITE); sk.selector().wakeup(); } } class Sender implements Runnable { public void run(){ // ... socket.write(output); if (outputIsComplete()) sk.cancel(); } } }
这里用到了Reactor模式。
关于Reactor模式的一些概念:
Reactor:负责响应IO事件,当检测到一个新的事件,将其发送给相应的Handler去处理。
Handler:负责处理非阻塞的行为,标识系统管理的资源;同时将handler与事件绑定。
Reactor为单个线程,须要处理accept链接,同时发送请求处处理器中。
因为只有单个线程,因此处理器中的业务须要可以快速处理完。
改进:使用多线程处理业务逻辑。
Worker Thread Pools
参考代码:
class Handler implements Runnable { // uses util.concurrent thread pool static PooledExecutor pool = new PooledExecutor(...); static final int PROCESSING = 3; // ... synchronized void read() { // ... socket.read(input); if (inputIsComplete()) { state = PROCESSING; pool.execute(new Processer()); //使用线程pool异步执行 } } synchronized void processAndHandOff() { process(); state = SENDING; // or rebind attachment sk.interest(SelectionKey.OP_WRITE); //process完,开始等待write事件 } class Processer implements Runnable { public void run() { processAndHandOff(); } } }
将处理器的执行放入线程池,多线程进行业务处理。但Reactor仍为单个线程。
继续改进:对于多个CPU的机器,为充分利用系统资源,将Reactor拆分为两部分。
Using Multiple Reactors
参考代码:
Selector[] selectors; //subReactors集合, 一个selector表明一个subReactor int next = 0; class Acceptor { // ... public synchronized void run() { ... Socket connection = serverSocket.accept(); //主selector负责accept if (connection != null) new Handler(selectors[next], connection); //选个subReactor去负责接收到的connection if (++next == selectors.length) next = 0; } }
mainReactor负责监听链接,accept链接给subReactor处理,为何要单独分一个Reactor来处理监听呢?由于像TCP这样须要通过3次握手才能创建链接,这个创建链接的过程也是要耗时间和资源的,单独分一个Reactor来处理,能够提升性能。