Our team is currently running stress tests and using JProfiler for monitoring.
We’ve noticed that when the number of concurrent threads goes up, not only does CPU usage spike, but the time it takes for WAITING threads to execute SQL statements in JPA views also increases. So, we decided to record both JPA views and HTTP Server views.
Since Full Sampling significantly affects the target server’s performance, we looked into the official documentation and switched to Async Sampling to see if it helps clarify the issue.
- JProfiler Help – Method call recording (ej-technologies.com)
Can we ask if Async Sampling is the right way of sampling for this kind of stress test? Will it impact the two views we’re currently recording?
Thanks!
We have already referred to the official documentation, but we are still not very sure.
Che ZY is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.