Kabir Khan wrote:
On 11 Feb 2010, at 23:23, Bill Burke wrote:
> BTW, my guess is that it is file caching. Good job though! Almost a
> full second shaved off. Nothing to sneeze about.
> So what's next for optimization?
In dependency the things which had the biggest impact were not breaking out of the
resolveContexts() loop and that AbstractDependencyItem was calling controller.getContext()
three times when a dependency is not there yet.
For me, profiling the whole app server startup gives too much information and different
hotspots don't really stand out that much. I'm creating a series of
micro-benchmarks to profile different areas in isolation. Next is trying the different
things in jboss-kernel, which is more interesting since it pulls in things like MDR and
jboss-reflect. I'll have a look at the ScopeKey lookups I mentioned in
today, before trying out other parts of
You can also filter per package/class within jprofiler. IMO, removing
everything in deploy/ is a good place to profile. Then stuff like
deployers, beans, jars, really shows up.
JBoss, a division of Red Hat