tomcat中的io处理
我注意到同一 tomcat 中的两个 servlet 和同一主机上的两个单独的 tomcat 之间的处理时间存在重大差异。 Servlet 使用 http 进行通信。 tomcat或java是否有某种机制可以在同一个tomcat或JVM中优化http通信。我试图确认这一观察结果与我正在运行的主机无关。
I noticed a major difference in processing time between two servlets in the same tomcat and two separate tomcats on the same host. The servlets communicate using http. Does tomcat or java have some mechanism that optimizes http communication when in the same tomcat or JVM. I'm trying to confirm this observation is not related to the host I'm running on.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这可能是阻塞 I/O 和非阻塞 I/O 之间的区别。
Tomcat 使用多线程模型：有一个用于处理请求的线程池和一个用于接收传入请求的队列。服务器分配一个线程来处理传入的请求，执行任务，发回响应，并将线程返回到池中。队列处理备份的请求。
Netty 采用的非阻塞 IO 是不同的。
也许这两个请求在被同一个Tomcat处理时正在排队。
It could be the difference between blocking and non-blocking I/O.
Tomcat uses the multi-thread model: have a pool of threads for processing requests and a queue for incoming requests. The server assigns a thread to an incoming request for processing, performs the task, sends back the response, and returns the thread to the pool. The queue handles requests that back up.
Non-blocking IO, as employed by Netty, is something different.
Perhaps the two requests are being queued up when they are processed by the same Tomcat.
有关这些测试的更多信息。两项测试均在 SunOS 5.10 上运行，并使用 Apache Tomcat 版本 6.0.20 和 jdk1.6.0_23。 http 传输可能涉及相当大的文件 - 5M。线程处理可能可以解释，但时间差异超过 10 倍让我怀疑没有数据需要从 JVM 传输出去。某种形式的阻塞与非阻塞可能适合时间差异。
Some more information about these tests. Both tests are run on SunOS 5.10 with Apache Tomcat Version 6.0.20 and jdk1.6.0_23. The http transfers can involve fairly large files - 5M. Thread handling might explain but with timing differences over a factor of 10 makes me suspect that no data has to transfer out of the JVM. Some form of blocking vs non-blocking might fit the timing difference.