blocks|key|4670648|text|如前所述，这似乎是一种“过早优化”的情况，但如果您真的想要提高性能，请尝试Simple+HTTP+Framework。或者像Jetty这样的小servlet容器。它们让你从一个非常基础的级别开始，你可以从那里发展你的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4670649|4670650|entityMap|0|LINK|mutability|MUTABLE|url|http://www.simpleframework.org/|1|http://jetty.codehaus.org/jetty/^0|11|L|0|1Q|5|1|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]|$A|S|B|T|1|U]]|C|$]]|$1|D|3|-4|5|6|7|V|8|@]|9|@]|C|$]]|$1|E|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|F|$G|$5|H|I|J|C|$K|L]]|M|$5|H|I|J|C|$K|N]]]]

As already mentioned, this seems like a case of "premature optimization", but if you really want to go for performance try the <a href="http://www.simpleframework.org/" rel="noreferrer">Simple HTTP Framework</a>. Or a small servlet container like <a href="http://jetty.codehaus.org/jetty/" rel="noreferrer">Jetty</a>. They make you start at a pretty basic level and you can evolve your application from there.

As soon as you hit a database though, the performance overhead from any application server or web framework will become insignificantly small.

blocks|key|2597172|text|看看Grails+Framework，在Apache+Tomcat上部署，以及当性能成为问题时，使用Terracotta进行扩展。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2597173|entityMap|0|LINK|mutability|MUTABLE|url|http://www.grails.org/|1|http://tomcat.apache.org/|2|http://www.terracotta.org/^0|2|G|0|K|D|1|1E|A|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

Take a look at the <a href="http://www.grails.org" rel="nofollow">Grails Framework</a>, deploy on <a href="http://tomcat.apache.org/" rel="nofollow">Apache Tomcat</a>, and when performance becomes an issue scale with <a href="http://www.terracotta.org/" rel="nofollow">Terracotta</a>.

blocks|key|2597286|text|我个人很喜欢tomcat上的tapestry，我们发布的一些应用程序拥有令人难以置信的高并发用户数，这是通过仔细的硬件选择、大量的性能测试以及使用Jmeter和分析工具优化应用程序代码来实现的。对于其他应用程序，j2ee正在发挥作用，所以我们讨论的是jboss之类的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2597287|对于您的需求，我要说的是:对servlet进行手工编码，并将其部署到jetty上。但remember...there不是金锤或银弹:-)+c2.com/cgi/wiki?GoldenHammer+c2.com/cgi/wiki？|2597288|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I personally enjoy tapestry on tomcat, and some of the applications we've put out have an incredibly high concurrent user count, achieved by careful hardware selection, much performance testing and optimizing of the application code with things like Jmeter and a profiling tool. For other applications, j2ee is in play, so we're talking jboss and the like.

To your requirements I say: handcode your servlets and deploy them on jetty. But remember...there is no golden hammer or silver bullet :-) c2.com/cgi/wiki?GoldenHammer c2.com/cgi/wiki?SilverBullet

blocks|key|2597343|text|网络调用最少的框架将是最快的。换句话说，使用哪个框架并不重要，因为等待网络会降低任何框架的性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2597344|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The framework that has the fewest network calls will be the fastest. In other words, it doesn't matter which framework you will use, as waiting on the network will kill performance in any framework.

I'm absolutely confused by all the choices out there. Glassfish, jersey, jax-ws, Grizzly, nginx, cherokee...all of them could be used as a web server and/or application server. 

Then there is the framework side. I want that side to be as small as humanly possible. I'm not very happy with the kind of frameworks I found in java, but this one looks good:
<a href="http://code.google.com/p/spark-java/" rel="nofollow">http://code.google.com/p/spark-java/</a>

But no mention of performance or anything. Does that mean that the server is mainly responsible for the performance and I can use 'spark' with something like nginx? Which would take care of all my performance problems? Maybe put Varnish in front of it for caching?

What is the simplest, fastest solution in java? I'd like something like tornado, gevent, nodejs...only in java.

What is the fastest java framework/server combo?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我完全被外面所有的选择搞糊涂了。它们中的Glassfish、jersey、jax-ws、Grizzly、nginx、cherokee...all可以用作网络服务器和/或应用服务器。然后是框架方面。我希望那一边尽可能小一点。我对我在java中找到的那种框架不是很满意，但是这个看起来不错：但没有提到性能或其他任何东西。这是...

问什么是最快的java框架/服务器组合？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是最快的java框架/服务器组合？EN