chriswhocodes/jitwatch

Log analyser / visualiser for Java HotSpot JIT compiler. Inspect inlining decisions, hot methods, bytecode, and assembly. View results in the JavaFX user...

View on GitHub ↗Jump to charts ↓Open shareable report →

chriswhocodes/jitwatch has 3k+ stars and 450+ forks on GitHub, is written in Java, and was last pushed on Sep 22, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:ApplicationCategory(s):Debugging & ProfilingDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on September 30th, 2013
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 461
Total Stargazers: 3,313 (+0)
Total Subscribers: 152 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.1 hours
Mean response time: 62.1 days
90th percentile: 234.1 days
Tracked items: 17

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 618 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

JITWatch is a log analyser and visualiser for the Java HotSpot JIT compiler.

JITWatch addresses the challenge of understanding JIT compilation behaviour in Java applications. It parses HotSpot compiler logs and presents the data through a JavaFX-based graphical interface, allowing developers to inspect inlining decisions, identify hot methods, examine bytecode, and view generated assembly code. This approach transforms dense compiler logs into navigable visualisations that reveal what the JIT compiler is actually doing with your code.

Developers optimising Java performance should use JITWatch when they need to understand why certain methods are or are not being inlined, which code paths are being compiled, and how escape analysis affects object allocation. It suits projects where JIT compilation behaviour is a performance concern and where developers want to move beyond guesswork about compiler optimisations. The tool requires either JDK11 or later with JavaFX available as a Maven dependency, or an earlier Java runtime that includes JavaFX built-in.

The project shows consistent maintenance with regular updates to the codebase and responsiveness to issues. Development activity includes ongoing refinement of the analysis capabilities and user interface, with commits addressing both bug fixes and feature improvements. The maintainer actively engages with the community through documentation and example resources.