Java Servlet容器性能如何？ [英] Java Servlet container performance?
问题描述
我想在这里向Java专家询问有关我将要进行的当前研究的问题-导致各种servlet容器效率差异的关键因素是什么？我需要比较Tomcat / JBoss / Glassfish / Jetty等，并且我需要知道哪些因素可能以最重要的方式影响结果？我将为此目的编写模拟应用程序，因此我可能会在其中实现任何有关Java功能/框架/库等的建议，这样我就可以大大增加容器的负载（实际上，我并不关心容器的负载）机器的负载，因为我当然要在同一台机器上运行所有测试），将不胜感激！我需要研究尽可能客观。谢谢您的帮助！
I'd like to ask the Java pros here a question about my current study that I am about to do - what are the key contributors to the differences in efficiency of various servlet containers? I need to compare Tomcat/JBoss/Glassfish/Jetty etc. and I need to know what "factors" may affect the results in the most significant way? I am going to write mock applications for that purpose, so any recommendation for a Java feature/framework/library etc. that I might implement there so that I can greatly increase the load of the containers (actually the containers, I do not care about the load of the machine since I am going to run all the tests on the same machine of course), would be appreciated! I need the study to be as objective as possible. Thanks for any help guys!
推荐答案
有些事情可能会对Web容器造成负担（当然，除了很多请求之外）：
Some things that could tax a web container (apart from lots of requests, of course):
- 使用小堆（例如，只有128或256 MB）
- 钝化会话（具有每个会话中都有较大的可序列化对象，太大而无法全部保留在内存中）
- 服务静态资源（很多小型或大型）
- 失败的请求（404或服务器错误）
- 包含许多其他JSP的JSP
- 大量不同的JSP
- 大量不同的servlet映射
- 大量链接的servlet过滤器
- 大量独立应用程序
- 重新部署应用程序（确保应用程序本身没有类加载器泄漏）
- Working with a small heap (e.g. only 128 or 256 MB)
- Passivating sessions (have large serializable objects in every session, too large to keep all in memory)
- Serve static resources (lots of small ones, or some big ones)
- Requests that fail (404 or server error)
- JSPs that include a lot of other JSPs
- Large number of different JSPs
- Large number different servlet mappings
- Large number of chained servlet filters
- Large number of separate applications
- Redeploying applications (make sure the apps themseves have no classloader leak)
这篇关于Java Servlet容器性能如何？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
