[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jetty-dev] ClasspathPattern.match
|
Simone,
I've done some initial profiling using Recoc, a JVM profiling agent I'm working on featuring a web UI backed by Jetty and Websockets :-)
Here's a live demo of Revoc instrumenting Jetty 8.1.8 on SVNSearch:
Anyhow, according to Revoc, ClasspathPattern.match has been run 321213 times, taking a total of 321ms. This is on a CMS based webapp with a pretty fat collection of libraries. (2800 classes loaded in the VM)
WebAppClassLoader.loadClass takes a total of 7060ms, so it seems that class path pattern matching is taking 4.5% of the classloading time. Given that profiling itself might slow down classloading, the percentage is probably larger when profiling is disabled.
Next step I'll try to confirm these findings using another profiler. Then I'll try optimizing and see if there is a win.
I do realize we're talking about tiny improvements, but Jetty's super fast startup is an important contributor to making it an attractive platform. I'd like to contribute my milliseconds if I can :-)
Thanks,
Eirik.