This article presents a comprehensive approach to reducing thread overhead in Android applications by detecting, counting, and consolidating thread creation through bytecode instrumentation, proxy thread pools, and stack size trimming, ultimately improving memory usage, CPU load, and UI smoothness.
Jetty’s ManagedSelector wraps the native NIO selector and, together with its ExecutionStrategy abstractions, merges I/O detection and handling in a single thread or adaptive pool, using strategies such as ProduceConsume, ProduceExecuteConsume, ExecuteProduceConsume, and EatWhatYouKill to maximize cache reuse and minimize context‑switch overhead in high‑concurrency applications.
This article explains the key performance metrics of backend systems—including QPS, TPS, response time, concurrency, and throughput—provides their definitions, relationships, practical calculation examples, and guidance on optimal thread counts for achieving balanced performance.
This technical guide explores Android out‑of‑memory crashes by classifying OOM into thread‑count, file‑descriptor, and heap‑memory issues, then details non‑intrusive thread and thread‑pool optimizations, file‑descriptor and I/O monitoring, image compression strategies, and both Java and native memory‑leak detection techniques.
This article shares practical configuration recommendations, system‑resource monitoring methods, and thread‑adjustment strategies for optimizing dble performance during BenchmarkSQL TPC‑C style load testing, highlighting how observable metrics guide effective tuning of the middleware and underlying MySQL nodes.
This article explains how Aspect‑Oriented Programming is applied in Android development to achieve non‑intrusive privacy compliance checks and thread‑usage optimization, detailing the use of compile‑time ASM bytecode instrumentation and runtime Xposed/epic hooks, along with code examples and measured performance gains.
This article details the systematic refactoring of Youku’s cross‑platform playback core, describing how redundant threads were removed, memory usage was cut by two‑thirds, and CPU‑driven power consumption was reduced, resulting in a leaner, faster, and more energy‑efficient SDK.
