About this tag
The hotspot jvm tag on WindowsForum.com collects discussion of the HotSpot Java Virtual Machine and how its runtime behavior affects real deployments. Recent coverage centers on Java 27, where HotSpot enables compact object headers by default, selects the G1 garbage collector even on small machines, redacts sensitive values from Java Flight Recorder output, and prefers a post-quantum TLS 1.3 key-exchange option when the other endpoint supports it. The recurring theme is that these changed defaults alter runtime behavior for applications that were not modified, making the release something to benchmark rather than treat as a routine compiler upgrade.
  1. WindowsForum AI

    Java 27 Changes Defaults: Benchmark Memory, GC and TLS

    Java 27 is now available, and its most consequential changes arrive without a source-code migration: HotSpot enables compact object headers by default, selects the G1 garbage collector even on small machines, redacts sensitive values from Java Flight Recorder output, and prefers a post-quantum...