0 views collected around this technical thread.
This article details how replacing Java's native double parsing with the Ryu and FastFloat algorithms, alongside JVM GC tuning, dramatically reduces CPU usage and latency in backend services, offering practical code examples, benchmark results, and actionable optimization strategies.
This article details a step‑by‑step experiment using SpringBoot 2.5.4 and JMeter to quantify how much heap memory a single HTTP or RPC request consumes, analyzes GC logs, presents code snippets for the test endpoints, and discusses the impact of logging and payload size on memory usage.
This article explains why the JVM throws java.lang.OutOfMemoryError: GC overhead limit exceeded, outlines common causes such as traffic spikes, memory leaks, insufficient heap and inefficient GC, and provides practical solutions and debugging steps to diagnose and fix the issue.
The article presents a Spring Boot experiment measuring per‑request heap memory usage for HTTP and RPC calls, details the JMeter test setup, analyzes GC logs, reports findings such as ~34KB per HTTP request and 0.5‑1MB per RPC request, offers optimization recommendations, and also includes promotional material for AI‑related products.
This article details a SpringBoot experiment using JMeter to measure the heap memory allocated per HTTP request, analyzes GC logs, and discusses how request size and logging affect memory consumption, providing practical JVM tuning insights for backend developers.
This article describes an experiment using SpringBoot 2.5.4 and JMeter to measure the heap memory allocated per HTTP and RPC request, detailing the setup, GC logging configuration, results showing average memory consumption around 34 KB per request, and recommendations for logging and performance optimization.
This article presents a comprehensive guide to PHP memory optimization, covering strategies such as using unset() to free variables, processing data in chunks, manual garbage collection, monitoring usage, optimizing loops, generators, lazy class loading, database tuning, profiling tools, serialization practices, Opcache, session handling, large file processing, and Composer dependency management.
This article details a practical experiment using SpringBoot 2.5.4 and JMeter to measure the heap memory allocated by individual HTTP and RPC requests, analyzes GC logs, and demonstrates how request size and logging affect memory consumption, providing insights for backend performance optimization.
This article presents a systematic experiment that uses JMeter to generate HTTP requests against a SpringBoot 2.5.4 service, records detailed GC logs, and calculates that each HTTP call consumes roughly 34 KB of heap memory, while logging and payload size can significantly increase the allocation.
This article demonstrates how to experimentally determine the heap memory allocated by individual HTTP and RPC requests in a SpringBoot application using JMeter load testing, GC logging, and code analysis, providing insights into memory consumption, GC frequency, and optimization strategies for backend performance.
The article details a SpringBoot experiment that uses JMeter to send 20,000 HTTP requests, captures detailed GC logs, and demonstrates that each request consumes roughly 34 KB of heap memory, with larger payloads and logging increasing the usage, highlighting the importance of memory‑aware coding and log management.
During performance testing of a Netty-based service, occasional message sends exceeded one second despite low CPU usage, prompting an investigation that identified a blocking ChannelHandler caused by a conditional sleep, leading to NioEventLoop thread stalls and delayed transmissions.
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 analyzes the memory increase observed after enabling Log4j2 asynchronous logging in Java services, examines root causes such as thread‑local reuse and large char[] allocations, and presents configuration and code changes—including disabling thread‑locals and limiting message size—to prevent heap growth and improve performance.
This article explains how using an off‑heap local cache (OHC) can dramatically lower GC pauses and cut interface latency by up to tenfold, covering the underlying principles, configuration, custom serializers, performance testing, monitoring metrics, and practical optimization recommendations for high‑traffic Java backend services.
The article describes a production OOM incident caused by downloading a 2.4 GB file, walks through GC log and heap‑dump analysis using MAT, identifies the problematic use of FileUtils.readFileToByteArray, and presents streaming and external storage solutions to prevent memory exhaustion.
This article demonstrates how to quickly locate and resolve frequent full GC and CPU spikes in Java backend services by combining Arthas‑integrated async‑profiler flame graphs with VisualVM, GCEasy analysis, and practical step‑by‑step deployment procedures.
This comprehensive guide presents a systematic, step‑by‑step process for diagnosing JVM memory problems—including heap, Metaspace, DirectMemory, JNI memory, and stack issues—using Alibaba Cloud ARMS, ATP, standard JDK tools, and best‑practice commands to quickly locate root causes and apply effective solutions.
This guide walks through systematic troubleshooting of Java applications by checking CPU, disk, memory, and network layers, using tools like jstack, jmap, vmstat, iostat, and tcpdump to pinpoint and resolve performance and stability problems.