Page History

...

GitHub Repository	https://github.com/Devexperts/aprof
Public Maven repo	https://bintray.com/devexperts/Maven/aprof
License	GPLv3
Contact

Using aprof

Download the latest version of aprof distribution, unzip, copy "aprof.jar" to your application's directory and run application with an additional JVM argument:

...

Do not rename agent file "aprof.jar", because it is configured by its name in manifest and will not work when renamed. 

Features overview

• Fast (can be used and is designed to be used in production) 
• Provides detailed information (can be used to identify problematic pieces of code)
• Configurable level of detail (as a compromise between speed and level of detail)
  

• Open Source (see, learn, improve)

Known issues

In current version (build 30):

• Does not work on JVM 1.8.0_20 and on JVM 1.7.0_65 (VerifyError on transformed classes) due to a bug in JVM: http://bugs.java.com/view_bug.do?bug_id=8051012 
  For Java 8, use 1.8.0_25 or later. For Java 1.7.0 use 1.6.0_60 or turn off verifier with "-noverify" option.
• Does not work on some releases of 1.6 (1.6.0_21 crashes with FATAL ERROR), but otherwise works in Java 5 to Java 8.
• Does not fully analyze inheritance hierarchy when tracking configured method invocations. It does not intercept locations of invocations of tracked methods that are performed via a sub-type that inherits the tracked method, It does misleadingly report invocation locations of a non-tracked method that happen to go via super-type that declares a tracked method for some other implementation of this type where this method is tracked. 
• Reports memory allocations that are performed in Java 8 during lambda capture of variables from scope as belonging to location in some internal "xxx$Lambda$xxx" class, not in the actual source code method that creates this lambda.
• Does not include Java 8 run-time library method (collections, streams, etc) in default list of tracked methods.

Origin and Goals

Java VM has an option -Xaprof printing how many instances of classes were allocated during lifetime of the application and how much memory they occupied in total and per instance. The option has no performance impact due to the fact that counting takes place during garbage collection. The only drawbacks are occasional overflows of counters and the absence of any information on locations where the object allocations take place.

...

• collecting information on locations where the object allocations take place. 
• providing an accurate profiling results.
• having very low performance impact (to be safely used in production environments).

When to use Aprof

Aprof should be used when the application spends a lot of time in garbage collection. Due to the specifics of Java VM, objects are allocated so fast that CPU profilers are unable to pinpoint the allocation hotspot. The only way is to use memory allocation profilers.

...

Aprof gets accurate profiling results and finds locations of object allocations at the same time being garbage-free and having very low performance impact.

How it works

See presentation on Joker Conference 2014: http://www.slideshare.net/elizarov/aprof-jocker-2014