Netty使用ExecutionHandler优化

	public ChannelPipeline getPipeline() throws Exception {
		// Create a default pipeline implementation.
		ChannelPipeline pipeline = pipeline();

		// Uncomment the following line if you want HTTPS
		// SSLEngine engine =
		// SecureChatSslContextFactory.getServerContext().createSSLEngine();
		// engine.setUseClientMode(false);
		// pipeline.addLast("ssl", new SslHandler(engine));

		pipeline.addLast("decoder", new HttpRequestDecoder());
		// Uncomment the following line if you don't want to handle HttpChunks.
		pipeline.addLast("aggregator", new HttpChunkAggregator(1048576));
		pipeline.addLast("encoder", new HttpResponseEncoder());
		// Remove the following line if you don't want automatic content
		// compression.
		pipeline.addLast("deflater", new HttpContentCompressor());
		

		//解决netty不响应请求的bug
		double coefficient = 0.6;  //系数
		int numberOfCores = Runtime.getRuntime().availableProcessors();
		int poolSize = (int)(numberOfCores / (1 - coefficient));

//		ExecutionHandler executionHandler = new ExecutionHandler(
//					new MemoryAwareThreadPoolExecutor(16, 1048576, 1048576)
//				);
<span style="color:#ff0000;">		ExecutionHandler executionHandler = new ExecutionHandler(
	             new OrderedMemoryAwareThreadPoolExecutor(16, 1048576, 1048576));</span>
		
		pipeline.addLast("execution", executionHandler);

		// pipeline.addLast("handler", new HttpRequestHandler());
		pipeline.addLast("handler", channelUpstreamHandler);
		return pipeline;
	}

当我们引入ExecutionHandler后，原本同步的ChannelHandler链在经过 ExecutionHandler后就结束了，它会被ChannelFactory的worker线程池所回收，而剩下的ChannelHandler链将由ExecutionHandler的线程池接手处理。

 在大多数情况下，我们会使用OrderedMemoryAwareThreadPoolExecutor，它的构造函数要求我们提供线程池的大小，在上面的代码中，我们使用了16这个具体的值，是一种很不好的写法，通常情况下，我们会使用配置文件使之可变，但是在实际部署时，并不能保证实施人员能很好的去调整，故提供如下的一种写法：

double  coefficient = 0.8 ;  //系数 int  numberOfCores = Runtime.getRuntime().availableProcessors(); int  poolSize = ( int )(numberOfCores / ( 1  - coefficient));

我们可以使用poolSize取代OrderedMemoryAwareThreadPoolExecutor(16, 1048576, 1048576)中的那个16，因为当一个系统被开发出来后，它是CPU密集型还是IO密集型是可评估的，通过评估其密集型，调整系数即可：CPU密集型接近0，IO密集型接近1。