The Java Virtual Machine (JVM) generates three key artifacts for performance optimization: Garbage Collection (GC) logs, Thread dumps, and Heap dumps. GC logs track memory management events, Thread dumps capture current thread states, and Heap dumps provide snapshots of memory. Each has specific uses in troubleshooting and performance analysis.
The article discusses the optimal strategy for application memory sizing: large memory with few instances or small memory with many instances. Two successful technology companies exemplify contrasting approaches. Both strategies can succeed, depending on team competence. Large memory is more expensive, but business needs may dictate memory requirements. Experience and emotions influence decisions.
You can configure JVM to invoke any script when OutOfMemoryError is thrown. Most of the time,OutOfMemoryError doesn't crash the application
To troubleshoot OutOfMemoryError, follow three steps: capture heap dump using JVM arguments to automate collection when errors occur, restart the application to maintain stability, and diagnose the problem using tools like Eclipse MAT or HeapHero for automated analysis. This approach can streamline the troubleshooting process significantly.