2008/8/1 Craig Walls <[EMAIL PROTECTED]> > > First, let me admit a bit of ignorance when it comes to profiling tools. > I've used them before, but I never feel like I really know what I'm > doing. That said... > > I have been unsuccessful in getting JProfiler to profile Pax Runner > running as a Windows Service. But I have been able to run it as a > standalone program (well...sorta...I'm using "jsl -debug" to run Pax > Runner from the jsl.ini configuration). What I seemed to have learned > (from the "Hotspots" tab) is... > > 66.1% of the time is spent in java.io.InputStream.read() with the bulk > of that time in org.ops4j.pax.runner.platform.internal.Pipe.run(). > 33.1% of the time is spent in java.lang.Process.waitFor() > 0.1% of the time is spent in java.util.jar.JarFile.getManifest() > > What's also interesting (at least as much as I can tell) is that all of > that time spent in org.ops4j.pax.runner.platform.internal.Pipe.run() > doesn't take place until after the platform has been started (the same > time that my CPU gets bombarded). > > Note again, however, that this profile was against the Pax Runner > running standalone (not as a Windows service). I do not have the same > CPU problems when I run it this way. But as a service, it hits 100% CPU > just about the same time that the platform starts. Unfortunately, the > service won't even start when I have it set to run with JProfiler. > > FWIW, here's the cmdline I'm giving to jsl.ini: > cmdline = -Xbootclasspath/a:C:/semantra/bin/agent.jar > -agentlib:jprofilerti -jar c:/semantra/bin/pax/pax-runner-0.12.0.jar > --platform=eq --noConsole --log=NONE > > I'll keep trying to start it as a service. >
I have access to a Windows machine - will take a look at this tomorrow -- Cheers, Stuart
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
