de9d91d4c7
Bumps [actions/setup-java](https://github.com/actions/setup-java) from 4.2.2 to 4.3.0.
- [Release notes](https://github.com/actions/setup-java/releases)
- [Commits](
|
||
---|---|---|
.devcontainer | ||
.github | ||
.mvn | ||
IT | ||
api | ||
gclogs | ||
images | ||
parser | ||
sample | ||
vertx | ||
.gitattributes | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
CONTRIBUTORS.md | ||
DEVELOPERS_GUIDE.md | ||
LICENSE | ||
NOTICES.md | ||
README.md | ||
SECURITY.md | ||
SUPPORT.md | ||
mvnw | ||
mvnw.cmd | ||
pmd-ruleset.xml | ||
pom.xml | ||
spotbugs-excludes.xml | ||
unifiedg1rules.txt |
README.md
Microsoft GCToolKit
GCToolkit is a set of libraries for analyzing HotSpot Java garbage collection (GC) log files. The toolkit parses GC log files into discrete events and provides an API for aggregating data from those events. This allows the user to create arbitrary and complex analyses of the state of managed memory in the Java Virtual Machine (JVM) represented by the garbage collection log.
For more detail you can read our Launch Blog Post.
Introduction
Managed memory in the Java Virtual Machine (JVM) is composed of 3 main pieces:
- Memory buffers known as Java heap
- Allocators which perform the work of getting data into Java heap
- Garbage Collection (GC).
While GC is responsible for recovering memory in Java heap that is no longer in use, the term is often used as a euphemism for memory management. The phrasing of Tuning GC or tuning the collector are often used with the understanding that it refers to tuning the JVM’s memory management subsystem. The best source of telemetry data for tuning GC comes from GC Logs and GCToolKit has been helpful in making this task easier by providing parsers, models and an API to build analytics with. You can run the Maven project HeapOccupancyAfterCollectionSummary sample as an example of this.
Usage
In order to use this library you'll need to add its dependencies to your project. We provide the instructions for Maven below.
Maven Coordinates
The GCToolKit artifacts are in Maven Central. You'll then need to add the api
, parser
and vertx
modules to your project in the dependencyManagement
and/or dependencies
section as you see fit.
<dependencies>
...
<dependency>
<groupId>com.microsoft.gctoolkit</groupId>
<artifactId>api</artifactId>
<version>3.0.4</version>
</dependency>
<dependency>
<groupId>com.microsoft.gctoolkit</groupId>
<artifactId>parser</artifactId>
<version>3.0.4</version>
</dependency>
<dependency>
<groupId>com.microsoft.gctoolkit</groupId>
<artifactId>vertx</artifactId>
<version>3.0.4</version>
</dependency>
...
</dependencies>
User Discussions
Meet other developers working with GCToolKit, ask questions, and participate in the development of this project by visiting the Discussions tab.
Example
See the sample project: sample/README
Contributing
See CONTRIBUTING for full details including more options for building and testing the project.
Test Coverage Report
License
Microsoft GCToolKit is licensed under the MIT license.