memstat-bench

Capture per-second memory timelines during vLLM-metal benchmarks and plot them.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/WindChimeRan/claude-dotfiles --skill memstat-bench
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memstat-bench
Source: https://github.com/WindChimeRan/claude-dotfiles/tree/main/skills/memstat-bench
Command: npx skills add https://github.com/WindChimeRan/claude-dotfiles --skill memstat-bench

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a per-second memory timeline during a vLLM-metal benchmark and plot it for visual analysis.

Core Features & Use Cases

  • Wired-memory timeline: 1 Hz samples of memory.wired_gb capturing Metal memory usage patterns.
  • Pressure tracking: 1 Hz samples of memory.pressure_percent to indicate OS pressure.
  • Used / active overlay: shows total system memory and active pages alongside wired memory.
  • Side-by-side comparisons: plot two runs on shared axes to highlight shape differences.

Quick Start

Run memstat-bench alongside your vLLM-metal benchmark to capture a per-second memory timeline and generate a combined plot.

Frequently Asked Questions about memstat-bench

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

FAQPage Schema
How do I visualize memory usage trends during a vLLM-metal benchmark?

Visualize memory usage trends during a vLLM-metal benchmark by running a sidecar logger that captures 1 Hz samples of wired memory and generates a timeline plot for visual analysis of memory shapes.

Why does my vLLM benchmark show high memory pressure on macOS Metal?

High memory pressure on macOS Metal during a vLLM benchmark is identified by capturing 1 Hz samples of memory.pressure_percent to track OS pressure levels alongside wired memory usage patterns.

What's the best way to compare memory shapes between two benchmark runs?

The best way to compare memory shapes between two benchmark runs is to plot them side-by-side on shared axes, highlighting differences in wired memory, active pages, and total system memory usage.

Do I need matplotlib and metalstat installed to track vLLM memory regressions?

Yes, you need metalstat on PATH and matplotlib in the vllm-metal environment to run the sidecar logger and generate the memory timeline plot required for memory-regression debugging.

Can I capture a per-second active memory timeline for vLLM-metal performance monitoring?

Yes, you can capture a per-second active memory timeline for vLLM-metal performance monitoring by sampling memory.wired_gb, memory.pressure_percent, and active pages at 1 Hz to reveal memory usage patterns.

When do I need a per-second memory timeline instead of just latency metrics?

You need a per-second memory timeline instead of just latency metrics when conducting memory-pressure investigations or regression debugging, allowing you to observe memory shapes and wired memory patterns rather than latency alone.