Confluence : Profiling using the YourKit Plugin
This page last changed on Sep 13, 2006 by mryall.
IntroductionThere is a plugin for Confluence 2.2 and later which allows easy profiling using the YourKit profiler. No license is required to generate a profile dump, but you will need at least an evaluation license to analyse the results.
Configuring YourKit in your JVMDownload YourKit for your platform, and follow the installation instructions. Your JVM will need to be configured to use the profiler. For the Sun 1.5 JVM on Linux, this is done with the agentlib parameter and by including the installation directory in the LD_LIBRARY_PATH environment variable, as shown below: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/to/yourKitAgent java -agentlib:yjpagent ... For configuration for other JVMs and platforms, see the YourKit documentation which is bundled with the installation. Installing the YourKit pluginDownload the plugin and upload it into Confluence through the Administration, Plugins page. A new menu option will appear under the 'Administration' heading. Click it and you should see the option to take a memory dump. This profiler dump will be saved to a local temp directory, and the path shown once it is complete. Why would I do this?Analysing a profiler dump enables Atlassian Support (or you, if you are interested) to see exactly what is happening in your application: what classes are using the memory, what is using CPU and so on. This can help us debug tricky performance problems which would otherwise be impossible to analyse remotely. Plugin source codeThe source code for this Confluence plugin is available from Subversion and browseable in Fisheye. To rebuild the JAR attached to this page, you need to run maven jar, and then extract the YourKit controller dependency (yjp-controller-api-redist-5.5.3.1.jar) and include that in the 'mashed' JAR too.
|
![]() |
Document generated by Confluence on Mar 22, 2007 20:55 |