简体   繁体   English

发送到 tomcat 的并发请求与 Dynatrace JVM 线程不匹配

[英]Concurrent requests being sent to the tomcat dont match with Dynatrace JVM threads

We are running performance test and using DynaTrace to monitor the run.我们正在运行性能测试并使用 DynaTrace 来监控运行。 While performance team claims to be sending concurrent requests to the tune of 900 at one point of time.而性能团队声称在某个时间点发送并发请求多达 900 个。 I don't see that being reflected on the DynaTrace JVM threads .Is this the right place to check this ON DT or there is something wrong in the test itself.我没有看到这反映在 DynaTrace JVM 线程上。这是检查这个 ON DT 的正确位置还是测试本身有问题。 Also Jmeter shows all the requests to be successfull. Jmeter还显示所有成功的请求。 Any pointers will be helpful任何指示都会有所帮助

hosts->Processes ->JVM metrics主机->进程->JVM指标在此处输入图像描述

Why you're asking us and not the "performance team"?为什么你要问我们而不是“表演团队”? If you think that here you will get a more comprehensive answer you need to provide way more information like JMeter's .jtl results file and report from its end.如果您认为在这里您将获得更全面的答案,您需要提供更多信息,例如 JMeter 的.jtl 结果文件并从其末尾报告。

  1. Given there is a spike from 250 to 500 threads JMeter generates some load, why your app is not kicking off 900 threads it's another question, I can think of the situation when the application is using Thread Pool pattern and it can serve the incoming requests without having to start as many threads as there are incoming connections鉴于有 250 到 500 个线程的峰值,JMeter 会产生一些负载,为什么您的应用程序没有启动 900 个线程,这是另一个问题,我可以想到应用程序使用线程池模式的情况,它可以在没有必须启动与传入连接一样多的线程
  2. JMeter needs to be properly tuned for high loads so ask the "performance team" if they're following JMeter Best Practices JMeter 需要针对高负载进行适当调整,因此请询问“性能团队”是否遵循JMeter 最佳实践
  3. JMeter treats HTTP status codes below 400 as successful, if there is a logical error in the script, ie all threads are stuck at login screen and cannot go further JMeter will report the responses as "successful", it makes sense to check request/response details using View Results Tree listener in order to ensure that the test is doing what it is supposed to be doing. JMeter 将HTTP 状态码低于 400 视为成功,如果脚本中存在逻辑错误,即所有线程都卡在登录屏幕并且无法继续 JMeter 将报告响应为“成功”,检查请求/响应是有意义的使用查看结果树侦听器的详细信息,以确保测试正在做它应该做的事情。 If it will turn out that it doesn't - consider adding ie Response Assertions to avoid such problems in the future如果事实证明不是 - 考虑添加 ie 响应断言以避免将来出现此类问题
  4. JMeter's workload pattern might be not properly configured on Thread Group level, the most common problem is that people forget to supply a sufficient amount of iterations, see JMeter Test Results: Why the Actual Users Number is Lower than Expected article for more information. JMeter 的工作负载模式可能未在线程组级别正确配置,最常见的问题是人们忘记提供足够数量的迭代,请参阅JMeter 测试结果:为什么实际用户数低于预期文章以获取更多信息。

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

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