Tomcat6.0.18还不错

我对Executor不太了解，但是我看他默认是注释，我就不太敢用了。不知道是不是不太成熟，才没有默认就采用这个配置? 因为我们是做Tomcat插件的产品的。大家都知道既然做产品就得尽量考虑周到。请有这个经验的说一下。如果已经比较成熟的话，我也一定要研究一下这个。

引用自：
Java Concurrency in Practice
By Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes, Doug Lea

Historically, operating systems placed relatively low limits on the number of threads that a process could create, as few as several
hundred (or even less). As a result, operating systems developed efficient facilities for multiplexed I/O, such as the Unix select and poll
system calls, and to access these facilities, the Java class libraries acquired a set of packages (java.nio) for nonblocking I/O. However,
operating system support for larger numbers of threads has improved significantly, making the thread-per-client model practical even for
large numbers of clients on some platforms.
[1]
[1] The NPTL threads package, now part of most Linux distributions, was designed to support hundreds of
thousands of threads. Nonblocking I/O has its own benefits, but better OS support for threads means that there
are fewer situations for which it is essential.

致谢！

我首先不否认这种说法的正确性。我在本地实验分别用NIO 和 IO 进行socket的读写，使用NIO不仅能大大提高速度，而且能够减少异常情况的出现。起码用NIO达到了我理想的效果，好像发送1K左右的info 20/s or 300/s。具体数据记不清了，但是感觉NIO效果不错。起码最简单的，对于数据缓存读写，而不是按位，感觉就好很多 。

其他的环境没有测试过。楼主引用的不知道是在什么环境下测试的结果。

恩,这个有必要用数据证实一下

直接对外会用一个比较单纯的 Http Server，如 Apache，IIS等

6.0.18 版有个EL表达式方面的bug，我改回16版了

我这里的结构是：squid + tomcat

tomcat不直接对外。

我是通过cacti来判断的。

我有一组集群的机器，我先升级了一般为tomcat6.0.18采用我所述的配置。
另外一半没有变。

在高负载的情况下，没有变动的服务器会出现cpu升高，load上升的情况。

而升级后的服务器的cpu和load非常稳定。

很好。

我一般不会太深入研究，主要就是根据实际情况，拿到产品环境试一下就知道那个好了。

一切来自实践。呵呵