JMnemohistosyne executes programmatically memory histogram of current process using available system jcmd command. Parses its output to get the number of instantiated classes and memory consumption of each class.
JMnemohistosyne uses the jmd command with the GC.class_histogram flag, that forces the execution of a full garbage collection. Remember that jcmd command is only available in JDK, not in JRE.
Full garbage collection and memory histogram are expensive operations. It is not recommendable to run JMnemohistosyne in production.
Only live objects are profiled and it inspects all objects in heap, used by your own code or by the JVM.
To get a histogram of all objects in memory you create a Histogramer object and call to the createHistogram() method, which will return a MemoryHistogram:
Histogramer histogramer = new Histogramer();
MemoryHistogram histogram = histogramer.createHistogram();
HistogramEntry arrayList = histogram.get("java.util.ArrayList");
System.out.println(arrayList.getInstances());
System.out.println(arrayList.getSize());
for (HistogramEntry entry : histogram) {
System.out.println(entry);
}MemoryHistogram class is an iterable collection of HistogramEntry objects containing: class name, number of instances and total size of all instances.
You can also search for a particular class by passing its full name to the get method.
All objects in memory are counted, created directly or indirectly by your code or by the JVM in its internal operations.
We can measure the number of living objects instantiated within a section of code using a lambda that contains it:
MemoryHistogram diff = Histogramer.getDiff(() -> {
HashMap<Integer, String> map = new HashMap<>();
for (int i = 0; i < 10000; i++) {
map.put(i, "" + i);
}
return map;
});
HistogramEntry nodes = diff.get("java.util.HashMap$Node");
System.out.println(nodes.getInstances());
System.out.println(nodes.getSize());Histogramer will take a snapshot of memory histogram before executing lambda code. After executing your code it creates other histogram and calculates the difference between both histograms.
You can put all the code you want and call all the needed code inside the lambda, but be sure that all the instances that you want to be taken into account are referenced by some object that already existed outside the lambda or are referenced by the object that returns the lambda (that implements Supplier<?>). Otherwise, by forcing the garbage collection the instances will not appear in the histogram and will be lost in memory, like tears in rain.
MemoryHistogram class is an iterable collection of HistogramEntry objects which contains: class name, number of instances and size of all instancess.
A MemoryHistogram can be filtered using the filter method with a varargs of:
- Class name including package:
java.util.HashMap - Class name with a final wildcard:
java.util.HashMap* - Class object:
HashMap.class - Regular expression patter over complete class name:
Pattern.compile(".*List")
MemoryHistogram filterd = histogram.filter("Object[]", "java.util.HashMap*", ArrayList.class, Pattern.compile(".*Hibernate.*"));All options are applied to the histogram and joined in a new MemoryHistogram.
JMnemohistosyne is uploaded to Maven Central Repository and to use it, you need to add the following Maven dependency:
<dependency>
<groupId>com.jerolba</groupId>
<artifactId>jmnemohistosyne</artifactId>
<version>0.2.3</version>
</dependency>in Gralde:
implementation 'com.jerolba:jmnemohistosyne:0.2.3'
or download the single jar from Maven Central Repository.
JMnemohistosyne depends on the presence of the jcmd command in the path. Then, check that the JDK is installed and is accesible from command line.
Currently it is tested in the CI system against: Oracle JDK 8, OpenJDK 8 and OpendJDK 11.
Feel free to dive in! Open an issue or submit PRs.
Any contributor and maintainer of this project follows the Contributor Covenant Code of Conduct.
Apache 2 © Jerónimo López