页缓存 / 脏页回写 / 内存回收诊断 Skill

Correlate system metrics with kernel tracepoints to diagnose memory reclamation and dirty page writeback issues.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill skill-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 页缓存 / 脏页回写 / 内存回收诊断 Skill
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/page-writeback-reclaim-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill skill-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, awk, grep, bc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses complex system performance issues related to memory pressure, page cache thrashing, and I/O backpressure, providing deep kernel-level insights without requiring manual intervention.

Core Features & Use Cases

  • Dual-Track Analysis: Combines real-time system metrics with kernel tracepoint events to correlate symptoms with root causes.
  • Automated Scenario Identification: Automatically categorizes issues into specific failure modes like dirty page writeback anomalies, kswapd CPU spikes, or I/O backpressure.
  • Use Case: When a production server experiences intermittent latency spikes or D-state process hangs, this skill identifies whether the root cause is an improperly configured vfs_cache_pressure or a slow disk device causing global I/O throttling.

Quick Start

Execute the page-writeback-reclaim-diagnosis skill to analyze the system memory state and identify potential reclaim or writeback bottlenecks.

Frequently Asked Questions about 页缓存 / 脏页回写 / 内存回收诊断 Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose Linux kernel dirty page writeback and memory reclamation bottlenecks?

To diagnose Linux kernel dirty page writeback and memory reclamation bottlenecks, this skill correlates real-time system metrics from /proc/vmstat and /proc/meminfo with kernel tracepoint events to perform automated root cause analysis.

Why does my Linux production server experience intermittent latency spikes and D-state process hangs?

Intermittent latency spikes and D-state process hangs often stem from I/O backpressure or memory pressure, which this skill identifies by categorizing issues into failure modes like dirty page writeback anomalies or kswapd CPU spikes.

How does correlating system metrics with kernel tracepoints identify I/O backpressure root causes?

Correlating real-time system metrics with kernel tracepoints identifies I/O backpressure root causes by automatically matching symptoms like global I/O throttling to specific configurations such as an improperly configured vfs_cache_pressure or slow disk devices.

Do I need specific command-line dependencies to troubleshoot memory pressure and page cache thrashing?

To troubleshoot memory pressure and page cache thrashing, you need command-line dependencies including bash, awk, grep, and bc to execute the scripts and process system metrics for comprehensive analysis.

Can I use this automated diagnosis skill for production servers experiencing kswapd CPU spikes?

Yes, you can use this automated diagnosis skill for production servers experiencing kswapd CPU spikes, as it automatically categorizes such anomalies and identifies whether they originate from memory reclamation or writeback faults.