This guide explains why Thread.stop() is unsafe, compares flag‑based, interruption‑based, and ExecutorService approaches, provides complete Java examples, usage steps, precautions, and advanced techniques for reliably stopping threads while releasing resources correctly.
This article explains how MySQL processes the KILL command, detailing the interaction between threads, the role of the kill flag, and the is_killed() function, all illustrated with diagrams and code examples to help readers grasp thread termination internals.
This article explains how Agrona's lightweight AgentRunner replaces the standard Java ExecutorService to manage long‑running tasks with minimal thread‑context switching, using the Agent model and customizable IdleStrategy to achieve high throughput and low latency in concurrent Java systems.
The article investigates why a RocketMQ consumer service running on a 4‑core ECS experiences sustained high load despite low CPU, I/O and memory usage, identifies excessive thread creation and frequent trace‑module context switches as the main causes, and proposes configuration and SDK upgrades to resolve the issue.
This article provides an in‑depth analysis of Druid's connection‑pool lifecycle, covering initialization, connection acquisition, validation, eviction, keep‑alive, and recycling processes, while offering performance‑related configuration recommendations and code examples for Java developers.
This article explains various ways to terminate a running Java thread, including using exit flags, the deprecated stop/suspend/resume methods, interrupt, handling InterruptedException, and the risks of forceful termination, accompanied by detailed code examples and best‑practice recommendations.
This article explains how pressing Ctrl+C in the MySQL client triggers a KILL QUERY command, details the server's multi‑step handling—including thread coordination, flag setting, and transaction rollback—and clarifies differences when autocommit is on or off.
This article explains how the HLL iOS driver team identified excessive global‑queue usage, thread‑switch overhead, deadlocks and UI‑thread violations, then introduced a priority‑aware queue pool, refined concurrency controls, and built long‑term monitoring to dramatically reduce crashes and improve performance.
This article explains the concept of thread pools, their performance benefits, the three native Java pool implementations, detailed internal mechanisms of ThreadPoolExecutor, task queue choices, rejection policies, and practical tuning advice for real‑world applications such as Tomcat and custom frameworks.
This article translates and expands on a HikariCP wiki post, explaining why smaller database connection pools often yield better performance, presenting benchmark videos and data, describing the underlying CPU, disk, and network constraints, and offering a simple formula to calculate an optimal pool size for typical server configurations.
This article explains how Java's ThreadPoolExecutor manages threads and tasks, covering the costs of thread creation, the roles of corePoolSize, workQueue, maximumPoolSize, rejection policies, keep‑alive time, and best practices for using bounded queues to avoid OOM.
This article explains what daemon threads are in Java, how they differ from user threads, the importance of setDaemon(true), provides the official setDaemon method documentation, and includes a complete demo program showing a daemon thread printing messages every second until the main thread ends.
The article explains Java’s ThreadPoolExecutor—its purpose, core design, lifecycle management, task scheduling, worker behavior, and typical configurations for fast response or batch processing—then proposes a dynamic pool with runtime‑adjustable core and max sizes, queue selection, and real‑time monitoring to prevent mis‑configuration and boost stability.
This article explains the iOS RunLoop mechanism, its role in keeping apps responsive, how it interacts with UIApplicationMain, timers, thread management, and various RunLoop modes, and provides practical examples for using RunLoop to maintain thread life cycles and improve UI performance.
Booster is a lightweight, scalable framework for mobile apps that improves performance, stability, and reduces APK size by using dynamic module loading, third‑party library injection, static‑analysis detection, bytecode‑based thread optimization, SharedPreferences tweaks, and resource compression, delivering over 10 MB size cuts, better crash detection, and non‑intrusive global optimization with full documentation.
The article explains why a Java‑based backend experiences higher CPU usage, reduced thread count, and frequent Young GC when traffic spikes, detailing the impact of Tomcat thread limits, JVM garbage‑collection pauses, and memory reclamation on overall service performance.
The article explains why an Android app’s main thread can be blocked by detailing Linux process versus thread concepts, the Completely Fair Scheduler’s priority and vruntime calculations, real‑time and nice priorities, and how Android uses cgroups and SchedPolicy enums to allocate CPU shares among foreground, background, and system threads.
This article explains Flutter’s cross‑platform engine architecture, detailing its four Task Runners, the Dart isolate model, platform‑specific implementations, custom thread configurations, and common pitfalls, helping developers understand and optimise performance for mobile apps.
This article provides a comprehensive overview of NFSv4’s design goals, security and performance improvements, and details the four major advantages of NFS‑Ganesha, its modular architecture, memory and thread management, caching mechanisms, and a practical Ceph RGW integration example.
The article outlines the step‑by‑step lifecycle of a database server—from system initialization and buffer allocation, through connection and thread management, request parsing, optimization, storage‑engine interaction, to final response delivery and cleanup—illustrated with diagrams of each stage.
