blocks|key|3725201|text|现在Visual+VM附带的性能分析器可以附加到正在运行的进程，至少可以给出性能的初步概述。它基于Netbeans分析器。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3725202|entityMap|0|LINK|mutability|MUTABLE|url|https://visualvm.dev.java.net/^0|2|9|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The <a href="https://visualvm.dev.java.net/" rel="nofollow noreferrer">Visual VM</a> profiler that now comes with the JDK can be attached to running processes and may at least give an initial overview of the performance. It is based on the Netbeans profiler.

blocks|key|1113256|text|试试jProfiler。它很容易与Tomcat集成|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1113257|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ej-technologies.com/products/jprofiler/java-profiler-J2EE.html^0|H|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Try jProfiler. It's easy to integrate with <a href="http://www.ej-technologies.com/products/jprofiler/java-profiler-J2EE.html" rel="nofollow noreferrer">Tomcat</a>

blocks|key|4570252|text|如果你能让Tomcat和你的应用程序在Netbeans中运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4570253|然后，您可以使用Netbeans内置的profiler来测试性能、内存使用情况等。|4570254|Netbeans中tomcat上的Wikipage。|4570255|entityMap|0|LINK|mutability|MUTABLE|url|http://www.netbeans.org/|1|http://profiler.netbeans.org/|2|http://wiki.netbeans.org/NetbeansedTomcat^0|J|8|0|0|J|8|1|0|H|8|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

If you can get Tomcat and your application running in <a href="http://www.netbeans.org" rel="nofollow noreferrer">Netbeans</a>. 

Then you can use the Netbeans built-in <a href="http://profiler.netbeans.org/" rel="nofollow noreferrer">profiler</a> to test performance, memory usage, etc ...

<a href="http://wiki.netbeans.org/NetbeansedTomcat" rel="nofollow noreferrer">Wikipage</a> on tomcat in Netbeans.

blocks|key|505322|text|我曾使用YourKit分析具有8+GB堆的应用程序，它工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|505323|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|$]]

I have used YourKit to profile applications with an 8 GB heap and it worked quite well.

blocks|key|1118810|text|检查JAMon。它不是一个分析器，但它是我可以推荐的最好的分析工具。它很容易与spring集成。我们在测试和生活环境中使用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1118811|entityMap|0|LINK|mutability|MUTABLE|url|http://jamonapi.sourceforge.net/^0|2|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Check <a href="http://jamonapi.sourceforge.net/" rel="nofollow noreferrer">JAMon</a>. It's not a profiler, but it's the best tool for profiling that I can recommend. It's very easy to integrate with spring. We use it in test and live environment.

blocks|key|3725174|text|我从来没有找到一种简单的方法来做到这一点，因为通常情况下发生的事情太多了，很难得到一个清晰的总体情况。对于Hibernate这样的事情更是如此，因为正确的行为可能是为缓存的数据抓取大块内存，即使你的应用程序并没有真正“做任何事情”，所以你运行的另一个内存效率低下的进程可能会被分析淹没。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3725175|你是在分析内存、速度，还是只是在寻找糟糕的性能？试着孤立地测试你怀疑是坏的进程，这肯定会容易得多。|3725176|JProbe，JProfiler，这两个都是好的，免费的演示。在IDE中测试会使内存问题变得复杂，我发现不去麻烦它更容易。|3725177|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I've never found an easy way to do this because there's typically so much going on that it's hard to get a clear overall picture. With things like Hibernate even more so because the correct behavior may be to grab a big chunk of memory for cached data, even though your app's not really "doing anything", so another memory inefficient process that you run may get swamped in profiling.

Are you profiling for memory, speed, or just in general looking for poor performance? Try to test processes that you suspect are bad in isolation, it's certainly much easier. 

JProbe, JProfiler, both good, free demos are available. Testing inside an IDE complicates the memory issues, I've found it easier not to bother.

blocks|key|1113374|text|试试JProfiler。它有一个试用许可，功能非常齐全。要使用它，您必须：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1113375|1113376|将JProfiler代理作为参数添加到java命令|unordered-list-item|1113377|启动服务器上的程序|1113378|启动JProfiler并选择"Connect+to+an+application+running+remotely“|1113379|为其提供端口号以及它在|1113380|上运行的任何主机<代码>F210|1113381|所有这些都在JProfiler附带的说明中，但重要的是，您将通过主机和端口连接到正在运行的应用程序。|1113382|至于要分析什么，我相信你对可能是内存/CPU密集型的事情有一个想法-加载大型数据集，排序，甚至简单的网络I/O，如果它做得不正确的话。做这些事情(如果您可以使用一些在服务器上运行的脚本自动执行负载测试，那就太好了)，并使用JProfiler收集快照。|1113383|然后在您空闲的时候查看图表。打开CPU监视并观察CPU周期被花费在哪里。您将能够在每个方法调用中按百分比缩小范围，因此，如果您在有源代码的方法中使用了超过1%25或2%25的CPU，请进行调查，看看是否可以减少对CPU的占用。|1113384|内存也是如此。禁用所有CPU分析，启用所有内存分析，再次运行测试并获取快照。|1113385|冲洗，重复。|1113386|您可能还会花时间阅读有关内存管理和垃圾收集的内容。当你已经在分析的时候，没有比调整垃圾收集更好的时机了：http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html|1113387|特别注意eden/survivor对象升级的部分。在web应用程序中，你会得到很多短暂的对象，因此以牺牲永久一代为代价来增加年轻一代通常是有意义的。|1113388|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ej-technologies.com/products/jprofiler/overview.html|1|http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html^0|2|9|0|0|0|0|0|0|0|0|0|0|0|0|0|1G|1J|1|0|0^^$0|@$1|2|3|4|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|D|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1I|8|@]|9|@]|C|$]]|$1|H|3|I|5|G|7|1J|8|@]|9|@]|C|$]]|$1|J|3|K|5|G|7|1K|8|@]|9|@]|C|$]]|$1|L|3|M|5|G|7|1L|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1M|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1N|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1O|8|@]|9|@]|C|$]]|$1|T|3|U|5|6|7|1P|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|X|3|Y|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Z|3|10|5|6|7|1S|8|@]|9|@$A|1T|B|1U|1|1V]]|C|$]]|$1|11|3|12|5|6|7|1W|8|@]|9|@]|C|$]]|$1|13|3|-4|5|6|7|1X|8|@]|9|@]|C|$]]]|14|$15|$5|16|17|18|C|$19|1A]]|1B|$5|16|17|18|C|$19|1C]]]]

Try <a href="http://www.ej-technologies.com/products/jprofiler/overview.html" rel="nofollow noreferrer">JProfiler</a>. It has a trial license and it is very full featured. To use it, you'll have to:

<ul>
<li>Add the JProfiler agent as an argument to your java command</li>
<li>Start the program on the server</li>
<li>Start JProfiler and choose the "Connect to an application running remotely"</li>
<li>Give it the port number and whatever host it's running on</li>
</ul>

All these are in the instructions that come with JProfiler, but the important part is that you'll connect through a host and port to your running app.

As for what to profile, I'm sure you have an idea of things that could be memory/CPU intensive - loading large data sets, sorting, even simple network I/O if it's done incorrectly. Do these things (it's great if you can automate load testing using some scripts that bang on your server) and collect a snapshot with JProfiler.

Then view the graphs at your leisure. Turn on CPU monitoring and watch where the CPU cycles are being spent. You'll be able to narrow down by percentage in each method call, so if you're using more than 1 or 2% of CPU in methods that you have source for, go investigate and see if you can make them less CPU intensive.

Same goes for memory. Disable all the CPU profiling, enable all the memory profiling, run the tests again and get your snapshot.

Rinse, repeat.

You might also take this time to read up on memory management and garbage collection. There's no better time to tune your garbage collection than when you're already profiling: <a href="http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html" rel="nofollow noreferrer">http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html</a>

Pay special attention to the part on the eden/survivor object promotion. In web apps you get a lot of short-lived objects, so it often makes sense to increase the young generations at the expense of the tenured generations.

I have a very large Java app. It runs on Tomcat and is your typical Spring/Hibernate webapp. It is also an extremely large Java program. It's easy for me to test the performance of database queries, since I can run those separately, but I have no idea to look for Java bottlenecks on a stack like this. I tried Eclipse's TPTP profiler, but it really didn't seem to like my program, and I suspect that it is because my program is too large. Does anyone have any advice on profiling a large webapp?

How can I profile a very large Java webapp?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有一个非常大的Java应用程序。它在Tomcat上运行，是典型的Spring/Hibernate webapp。它也是一个非常大的Java程序。测试数据库查询的性能对我来说很容易，因为我可以单独运行它们，但我不知道在这样的堆栈上寻找Java瓶颈。我尝试过Eclipse的TPTP分析器，但它似乎真的不喜欢我的程序，我怀疑这是因为我的程序太大了。有没有人对分析一个大型webapp应用有什么建议？

问如何分析一个非常大的Java webapp？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何分析一个非常大的Java webapp？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何分析一个非常大的Java webapp？
EN