Re: [jboss-as7-dev] AS 7 profiling output while running under load
One of the things to note, is that the CPU percentages seem very small. Having said that,
its actually counting each CPU cycle available on the entire system. On my test system I
have 16 virtual cores, so 1600% would be 100% CPU utilization.
So, a small percentage, like 1 or 2% is actually quite a bit of CPU cycles.
Andy
----- Original Message -----
From: "Scott Marlow" <smarlow(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Saturday, May 21, 2011 11:38:30 AM
Subject: [jboss-as7-dev] AS 7 profiling output while running under load
You probably saw Andy Miller's notes, explaining how to profile AS7
with
the oprofile tool on Fedora
(http://community.jboss.org/wiki/ProfilingAS7UsingOProfileOnFedora).
http://pastebin.com/ewvCdC48 contains output from a performance test.
I
wanted to share this with everyone, as its interesting to see how
much
CPU is used by various parts of our codebase. Take the information
with
a grain of salt, as its not that meaningful by itself.
This could probably be combined with a traditional profiler (which
would
show the reason why something was called thousands of times). But at
least this gives you an idea of which code to focus on.
I'm still trying to understand what some of the oprofile details mean
exactly as well.
Scott
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev