Fully featured low overhead profiler for Java EE and Java SE platforms.
Monitoring and profiling solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Export of profiling results to HTML, CSV, XML, plain text

You can export all reports and data to:

  • HTML, optionally packing all generated files to a single ZIP archive
  • CSV ("comma separated values") format
  • XML
  • Plain text format

Export from UI

Use File | Export to... (Ctrl+S) to export current view:

To export telemetry data, right-click a graph to invoke a popup menu:

File | Copy To Clipboard... (Ctrl+C or another platform specific shortcut) action copies text of selected row in all trees and lists.

Export with command line tool

You can automatically export some basic views using the following command:

java -jar <Profiler Installation Directory>/lib/yjp.jar -export <snapshot file> <target directory>

Note: the target directory where the resulting files will be created must exist when you issue the command.

Exported views

The following views can be exported:

  • Class list - for memory snapshot
  • Class loaders - for memory snapshot
  • Method list (CPU) - if recorded
  • Call tree (CPU) - if recorded
  • Method list (allocations) - for memory snapshot, if allocations recorded
  • Method list (garbage collection) - for memory snapshot, if allocations recorded
  • Summary
  • Probe tables
  • Telemetry graphs

By default, all the views are exported, if corresponding data is present in the snapshot.

To export only particular views, specify one or several of the following system properties:

  • export.class.list
  • export.class.loaders
  • export.method.list.cpu
  • export.call.tree.cpu
  • export.method.list.alloc
  • export.method.list.gc
  • export.summary
  • export.probes
  • export.charts

If at least one of the properties is specified, only specified views will be exported. If none of the properties is specified, all available views will be exported.

By default, filters are not applied when exporting call trees and method lists, in order to provide all available profiling information for further processing. Thus the results may look differently than in the UI where the filters are applied by default. To apply the filters to the exported results, specify system property

  • export.apply.filters
  • Example:

    • java -Dexport.method.list.cpu -Dexport.class.list -Dexport.apply.filters -jar /usr/yjp/lib/yjp.jar -export foo.snapshot outputDir - export CPU method list and class list only, and apply the filters
    • java -jar /usr/yjp/lib/yjp.jar -export foo.snapshot outputDir - export all available views, the filters will not be applied

    Export formats

    By default, views are exported in each of applicable formats (HTML, CSV, XML, plain text).

    To export in only particular formats, specify one or several of the following system properties:

    • export.txt
    • export.html
    • export.csv
    • export.xml

    If at least one of the properties is specified, export will be performed in only specified format(s). If none of the properties is specified, export will be performed in all formats available for each of the views.

    Example:

    • java -Dexport.method.list.cpu -Dexport.class.list -Dexport.txt -jar /usr/yjp/lib/yjp.jar -export foo.snapshot outputDir - export CPU method list and class list only, and only as text
    • java -Dexport.csv -jar /usr/yjp/lib/yjp.jar -export foo.snapshot outputDir - export all available views, and only as CSV
    • java -jar /usr/yjp/lib/yjp.jar -export foo.snapshot outputDir - export all available views in all available formats