简体繁体 English

Kony Web 应用程序在并发服务调用上有 Object.wait()

[英]Kony Web Application is having Object.wait() on Concurrent Service Calls

原文 2020-01-06 17:06:54 6 1 java/ websphere/ java.util.concurrent/ temenos-quantum/ dynatrace

While executing a performance test of 150 users using SilkMeter for Kony Web Application, we came across a strange behavior where services are held on wait state on the doFilter method.在使用 SilkMeter for Kony Web Application 对 150 个用户执行性能测试时，我们遇到了一个奇怪的行为，即服务在 doFilter 方法上处于等待状态。

The application is running on IBM WebSphere 8.5.10 and web thread is configured as min 50 and max 800. The issue is when we increase the number of users, the wait() method is also increasing in time.该应用程序在 IBM WebSphere 8.5.10 上运行，Web 线程配置为 min 50 和 max 800。问题是当我们增加用户数时，wait() 方法也随着时间增加。 Below is a screen captured from Dynatrace.下面是从 Dynatrace 捕获的屏幕。 [![Dynatrace report][1]][1] [![Dynatrace 报告][1]][1]

We tried many methods but couldn't get rid of this wait method.我们尝试了很多方法，但无法摆脱这种等待方法。 Any suggestions?有什么建议？

1 个解决方案

This is the expected behavior of Kony which is tested in 7.3.0 version.这是在 7.3.0 版本中测试的 Kony 的预期行为。 This happens when the Transactions per hour increases.当每小时交易量增加时会发生这种情况。 When there are many server hits, due to kdw, we can see a wait time.当有很多服务器命中时，由于kdw，我们可以看到等待时间。 If this increases beyond, 5 seconds, then it's better to reduce the Transactions and think time of silk meter.如果这增加超过5秒，那么最好减少丝绸计的事务和思考时间。 Kony supports 35 requests per sec for 1 CPU and 8 GB memory.对于 1 个 CPU 和 8 GB 内存，Kony 支持每秒 35 个请求。 Exceeding this would increase wait time as shown in the figure.超过此值会增加等待时间，如图所示。