Upload a GC log to see summary, analytics, and per feature charts of a Java app's garbage collection behavior.
Diagnose Java memory pauses or leaks by visualizing G1, Parallel, Serial, CMS, or ZGC log data.
Run the tool as a Docker container in a CI pipeline to review GC health after each build.
| kcpeppe/gcsee-jma | zjuncher/yunqi-youxiang | happynewyear1995/uba-x | |
|---|---|---|---|
| Stars | 42 | 44 | 47 |
| Language | Java | Java | Java |
| Setup difficulty | moderate | moderate | hard |
| Complexity | 2/5 | 3/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Java 25+ or Docker, plus a GC log file to analyze.
gcsee-jma is a Java Memory Analyzer built on the Quarkus web framework. It takes a garbage collection (GC) log file produced by a running Java program and turns it into an interactive web dashboard, with a summary view, analytics, and charts broken down by feature. It supports logs from several garbage collectors, including G1, Parallel, Serial, CMS, and generational ZGC, and it is built on top of an existing parser called GCSee. There are two ways to run it. The simplest is to download the release jar file from the project's Releases page and run it directly with Java 25 or newer, from any vendor such as Temurin, Oracle, or Azul. After a few seconds the app starts a local web server, and you open it in your browser to upload and analyze a GC log. The second way is to run it as a container with Docker, which bundles its own Java runtime so you do not need one installed. Both the standalone jar and the container image are published for each release, and the container supports both Intel and Apple Silicon machines. If you want to build the project from source instead of using a release, you need JDK 25 and Maven 3.9 or newer, and can use Maven commands to build a runnable jar or run the app in a hot reload development mode. This tool is aimed at Java developers and performance engineers who need to understand why a Java application is pausing, running out of memory, or behaving unpredictably, by visualizing what its garbage collector was actually doing over time. Releases are automated: pushing a version tagged commit triggers a workflow that builds the jar, publishes a GitHub release, and builds and pushes the container image.
A Quarkus web app that turns a Java garbage collection log into an interactive dashboard of charts and analytics.
Mainly Java. The stack also includes Java, Quarkus, Docker.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.