0 views collected around this technical thread.
This article explains why collection‑level OutOfMemoryError occurs in Java services, presents two core solutions—code‑level pagination using Stream and database queries, plus hardware upgrades and cloud server scaling—to prevent heap overflow and improve backend performance.
After upgrading to JDK 11 and switching to G1GC, the author observed memory usage exceeding 90% due to G1 Old GC not reclaiming space, and provides a detailed analysis of the issue, including heap inspection, GC mechanisms, and practical tuning solutions such as adjusting heap size and G1GC parameters.
This article details a real‑world case where Spring Boot microservices on a 64 GB server consumed excessive memory, explains how to diagnose the issue using jps and jmap, discusses default JVM heap settings, and provides practical recommendations for tuning JVM parameters to prevent similar problems.
This article records and reviews a production incident where multiple Spring Boot services consumed excessive memory, explains how default JVM settings caused each instance to allocate up to 12 GB of heap, and provides step‑by‑step diagnostics, configuration guidelines, and optimization recommendations for backend developers.
This article demonstrates how to quantify the heap memory allocated by individual HTTP and RPC calls in a SpringBoot application by creating a test service, configuring JMeter for load, capturing detailed GC logs, and analyzing the results to guide JVM and logging optimizations.
This article presents a SpringBoot-based experiment measuring the heap memory allocated per HTTP request, detailing the setup with JMeter, JVM GC logging, observed memory usage of roughly 34 KB per request, analysis of GC frequency, and concludes with recommendations on logging and memory optimization, while also promoting related AI services and community resources.
This article explains how to avoid OutOfMemoryError when exporting massive MySQL datasets by streaming data with JPA or MyBatis, writing each record directly to a CSV file, and provides complete Spring Boot code examples, performance comparisons, and deployment tips.
The article explains that Android OOM crashes often stem from oversized bitmaps, showing how a 36 KB image can consume 2.4 MB RAM, compares Glide and Picasso scaling, recommends using appropriate bitmap configs (ARGB_8888 vs RGB_565), matching image dimensions to view size, and provides Kotlin Glide module code for dynamic format selection to optimize memory usage.
This article examines how memory usage affects Android app performance, analyzes system and process-level impacts, discusses GC behavior, identifies common memory issues such as leaks, image loading, and memory churn, and provides practical optimization techniques and tool-based solutions to reduce memory consumption and prevent OOM and lag.