简体   繁体   English

YourKit in Production

[英]YourKit in Production

I have recently downloaded a trial version of YourKit and after playing with it for a while it looks great, but I am concerned about running it in the production environment. 我最近下载了YourKit的试用版,在玩了一段时间之后看起来很棒,但我担心在生产环境中运行它。 Previous profilers I have used have put unacceptable overhead on the servers. 我使用的以前的分析器在服务器上放置了不可接受的开销。

Does anyone know the typical overhead of the YourKit software? 有谁知道YourKit软件的典型开销? Or has anyone had any problems running YourKit in a production environment? 或者有任何人在生产环境中运行YourKit有任何问题吗?

I am running YourKit for Java. 我正在运行YourKit for Java。 The server I am profiling is RedHat running JBoss 4. 我正在分析的服务器是运行JBoss 4的RedHat。

For everbody wondering: Initially we already have had really strange performance issues, which we couldn't place for quite a while. 对于有人想知道:最初我们已经有了非常奇怪的性能问题,我们不能放置很长一段时间。

So we installed yourkit on our production servers (Tomcat) and disabled the telemetry (disableexceptiontelemetry,disablestacktelemetry) as advised. 因此,我们在生产服务器(Tomcat)上安装了yourkit,并根据建议禁用了遥测(disableexceptiontelemetry,disablestacktelemetry)。 Then we started tuning the Garbage Collection but this did not seem to make any difference. 然后我们开始调整垃圾收集,但这似乎没有任何区别。 Still from time to time randomly one of the servers would start to show real bad performance. 有时候,其中一台服务器会开始显示出真正糟糕的性能。 Sometimes it did recovered by itself, more often a restart was the only solution. 有时它确实自行恢复,更常见的是重启是唯一的解决方案。

After a lot of debugging & log-reading we found some very long periods of reference checking concerning the JNI Weak References in the gc log. 经过大量的调试和日志读取后,我们在gc日志中发现了一些关于JNI弱引用的很长时间的引用检查。 The probes of yourkit seemed to mess with that somehow. 你的探针似乎以某种方式混乱了。

After disabling the probes as well (builtinprobes=none) everything got back to normal. 在禁用探针之后(builtinprobes = none)一切都恢复正常。 The tuning of the gc config had solved our initial performance problems already, but leaving the yourkit probes active created a new issue, which was so similar, that we couldn't tell them apart. 调整gc配置已经解决了我们最初的性能问题,但是让你的探测器活动保持活动状态会产生一个新问题,这个问题非常相似,我们无法区分它们。

See here for more details: 有关详细信息,请参见此处
Java G1 GC Processing Reference objects works slow Java G1 GC Processing Reference对象运行缓慢

I have used Yourkit on JBOSS and Mule servers in production. 我在JBOSS和Mule服务器上使用了Yourkit进行生产。 What I felt is that when the load increases , it is throwing out of memory error. 我的感觉是,当负载增加时,它会丢失内存错误。 Then we stopped using it in production and we use it only for local testing. 然后我们停止在生产中使用它,我们仅将其用于本地测试。

And we use Jconsole in production server to monitor server resources like CPU , memory,Threads. 我们在生产服务器中使用Jconsole来监视服务器资源,如CPU,内存,线程。

It is really helpful. 这真的很有帮助。

I have used yourkit in production but on a tomcat server. 我在生产中使用了yourkit但是在tomcat服务器上。 It works pretty well and we didn't noticed any major performance overheads. 它工作得很好,我们没有发现任何重大的性能开销。

We had many instances of Tomcat server running behind a load balancer. 我们有许多Tomcat服务器在负载均衡器后面运行的实例。 So we put yourkit on one of the servers and things work out pretty well. 所以我们把你的套件放在其中一台服务器上,事情很顺利。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM