However, there's a trade-off: . Each object reference in the heap grows from 4 bytes (32-bit) to 8 bytes (64-bit). This increases memory consumption by approximately 30–50% for the same application, unless you enable Compressed Oops (Ordinary Object Pointers). Compressed Oops: The Game Changer Since Java 7 (and improved in Java 8+), the JVM can use compressed pointers :
If you're still running production apps on a 32-bit JVM, ask yourself: Is it because you genuinely need less than 2 GB of heap, or because you haven't migrated yet? In most cases, the answer is the latter. Make the leap to 64-bit Java—your future self (and your memory-hungry application) will thank you. Have you migrated a large application to 64-bit Java? Share your experience in the comments below. java 64
java version "17" 2021-09-14 LTS Java(TM) SE Runtime Environment (build 17+35) Java HotSpot(TM) 64-Bit Server VM (build 17+35, mixed mode, sharing) Alternatively, programmatically: However, there's a trade-off: