This article explains Flink's core execution‑resource concepts—including operator chaining, task slots, slot‑sharing groups and co‑location groups—detailing their conditions, API controls, internal implementation, and how they together maximize throughput and resource utilization in stream processing.
The article outlines how to boost system performance through algorithmic refinements, hardware and software resource upgrades, interaction optimizations between algorithms and resources, and effective caching techniques, while acknowledging trade‑offs and the need for balanced decisions.
This article details JD.com's journey from physical servers to a massive Docker‑based cloud‑native platform, covering challenges, architecture, elastic scheduling, monitoring, and resource‑driven operations that support tens of thousands of containers across multiple data centers.
Closing database connections promptly is essential for performance and availability, and this guide explains practical rules, connection‑pool benefits, safe coding patterns, exception handling, and how to diagnose lingering connections using MySQL's SHOW PROCESSLIST command.
This article explains how Ctrip’s Android app adopted a plugin‑based, dynamic‑loading framework to overcome method‑limit, improve build speed, enable hot‑deployment, and support modular A/B testing, detailing the underlying principles, compilation changes, runtime resource and class loading, and the trade‑offs involved.
This article details how the e‑commerce company 1号店 selected the Storm framework to create a low‑cost, highly available, and easily scalable distributed stream‑processing system, covering architecture design, resource isolation with CGroup, custom UI improvements, and operational lessons for handling massive traffic spikes.
This article demystifies PHP’s internal architecture, covering its design philosophy, four‑layer system, SAPI interfaces, execution flow with opcodes, the Zend hash table, variable handling via zval, reference counting, and resource management, providing a comprehensive guide for backend developers.
The article shares the author’s experience designing and operating enterprise‑grade cloud platforms, covering resource and application management, the Platform EGO architecture, comparisons with Mesos, Yarn and Kubernetes, and practical insights on scaling, scheduling, security, and architectural evolution.
This article explores how enterprise‑level web teams can move beyond classic Yahoo performance rules by using hash‑based static asset versioning, dependency‑driven templates, and smart bundling to reconcile engineering constraints with front‑end optimization goals.
This article explains how Docker uses Linux namespaces and cgroups to provide isolation, CPU/memory/I/O control, and monitoring, and includes practical scripts and tips for managing container resources effectively.
This article explains Linux cgroups—its subsystems, hierarchical structure, kernel implementation via VFS, mounting and configuration methods, and practical examples—showing how they provide fine‑grained resource control for processes and containers.
An experienced backend engineer shares practical strategies to prevent service failures, covering third‑party distrust, user‑side safeguards, robust API design, traffic limiting, resource management, and architectural best practices such as single‑responsibility and avoiding single points of failure.
Voidbox integrates Docker containers with YARN to simplify distributed application development, improve deployment, boost cluster efficiency, and provide fault‑tolerant, DAG‑based execution modes, enabling seamless resource management for Hadoop‑based big data jobs.
The article outlines a comprehensive approach to performance tuning by first optimizing algorithms, then enhancing hardware and software environments, and finally improving the interaction between code and resources through load balancing, caching, and I/O reduction, while acknowledging trade‑offs such as consistency and operational complexity.
The article outlines how narrowing operational permissions, automating processes, and adopting data‑center operating systems enhance security, scalability, visibility, and fault handling while reducing manual effort and enabling rapid, low‑risk changes across large infrastructures.
The article reviews Google’s Borg paper, highlighting how Borg distinguishes production and non‑production tasks, manages jobs and containers, improves utilization through mixed‑workload scheduling, enforces isolation via overload and over‑commitment controls, and compares Borg’s approach to other cluster managers.
This guide explains how Linux manages CPU scheduling fairness and demonstrates three practical methods—nice, cpulimit, and control groups—to prioritize, limit, or allocate CPU resources for processes, complete with compilation steps, command examples, and performance observations using top.
In a Baidu technical salon, Xu Liqiang detailed the evolution of Baidu’s private‑cloud platform—covering unified resource pooling, performance‑cost balanced resource management, demand‑driven tiered release, and automated elastic services that together support rapid product‑line iteration across services like Tieba, Community, Search, and Mobile Cloud.
