Profiling with YourKit


Here the server refers to the machine on which you run your application server, and the client to the machine on which you run the YourKit UI. In some cases, for instance if you are running the application server and YourKit on your development machine, the server and client will be the same machine.
  1. On the server, make the profiler agent library available to the JVM by changing the PATH on Windows, the LD_LIBRARY_PATH on UNIX, or the DYLD_LIBRARY_PATH on OS X. See enabling profiling manually for more details on this.
  2. Start YourKit and connect to the local or remote application.

Memory usage

After you've "hit" your application with a browser or testing tool, click on the Capture Memory Snapshot button.

You can save memory snapshots and pass them along to other developers who can then analyze them.

CPU usage

After you warmed up the JVM with a few requests, click the Start CPU Profiling button (the second one in the following screenshot). Then "hit" the server with the requests you would like to profile. When done, click the Capture Performance Snapshot button (the first one in the following screenshot).

This creates a snapshot, which, like memory snapshots, you can pass along to other developers for analysis.