This article details troubleshooting StarRocks write failures caused by THRIFT_EAGAIN timeouts, analyzing JVM memory patterns, Thrift RPC behavior, TRUNCATE TABLE resource overhead, and resolving the issue by increasing thrift_rpc_timeout_ms from 5s to 30s while planning long-term architectural improvements.
This article explains common CPU and JVM memory bottlenecks in Java applications, shows how to detect abnormal usage with monitoring and alerts, and provides step‑by‑step methods—including top, jstack, flame‑graph analysis, and APM tools—to pinpoint and resolve performance hotspots efficiently.
This guide explains how to adjust IntelliJ IDEA's maximum heap size and edit custom VM options to achieve a better balance between performance and overall system memory usage, based on insights from previous IDEA performance testing.
This article shares practical methods and real‑world case studies for IT professionals to analyze, locate, and fix system runtime issues, service timeouts, file‑handle leaks, JVM memory overflows, and performance bottlenecks, emphasizing hypothesis testing, boundary narrowing, and systematic post‑mortems.
This article demystifies Java’s parameter passing mechanism by clarifying the distinction between primitive and reference types, illustrating how assignment and method calls affect values and objects, and explaining the underlying JVM memory model, stack, heap, and array handling with clear code examples.
This article reports a systematic experiment that compares four IntelliJ IDEA memory configurations on a MacBook Pro, measuring startup time, project loading speed, and garbage‑collection behavior with jstat, and concludes that allocating more heap (2‑4 GB) significantly improves IDE responsiveness for large codebases.
This article explains the distinction between value passing and reference passing in Java by examining the JVM memory layout, the roles of the stack, heap, and method area, and demonstrates how primitive and object parameters behave through detailed code examples and visual diagrams.
This article explains why Java treats all method arguments as value‑passed, explores the JVM memory model, distinguishes between primitive and reference types, and demonstrates through code examples how parameter passing affects variables and objects in practice.
