Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

System Overload

Moderators: Vladimir Kondratyev, Anton Katilin

System Overload

Postby elidan1 » Fri Oct 08, 2004 6:11 pm

We are trying to profile a "medium size" application running on Tomcat 5.
The problem is that the profiler seems to add an inordinate amount of load to the system - response times up to 30 seconds for a 10 users load created with jmeter. We can run up to 75 concurrent users without the profiler.
Is this by design, or are we doing something wrong?
Posts: 1
Joined: Fri Oct 08, 2004 6:00 pm

Postby Vladimir Kondratyev » Fri Oct 08, 2004 7:29 pm

Profiler overhead depends on the tasks you are performing. For example, recording of object allocations or CPU tracing can significially slow down the profiled application. So you do need to turn on recording of object allocations if you are not finding garbage allocation spots. "sampling" is also very good for CPU profiling (but is a bit less precise then tracing).
Vladimir Kondratyev
Posts: 1518
Joined: Tue Aug 10, 2004 7:52 pm
Location: Düsseldorf, Germany

Return to Java Profiler

Who is online

Users browsing this forum: No registered users and 1 guest


YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy.