openclaw-test-performance

Profile OpenClaw test suite bottlenecks with vitest and pnpm.

1|Updated Mar 6, 2026

Search Tags:#vitest #performance #pnpm #profiling #benchmark #openclaw

Ready to run

npx skills add https://github.com/zhcndoc/openclaw --skill openclaw-test-performance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openclaw-test-performance
Source: https://github.com/zhcndoc/openclaw/tree/main/.agents/skills/openclaw-test-performance
Command: npx skills add https://github.com/zhcndoc/openclaw --skill openclaw-test-performance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenClaw's test suite can become slow and memory-hungry; this Skill provides structured benchmarking, diagnostics, and guidance to speed up tests, reduce CPU load, and manage RSS.

Core Features & Use Cases

Baseline benchmarking: establish performance baselines for the test suite and key subsystems.
Hotspot diagnosis: identify import hotspots, inefficient tests, and large memory footprints to target optimizations.
Guided optimization: propose repeatable steps to improve speed while preserving code coverage and reliability.

Quick Start

Run the full benchmarking workflow to establish a baseline and identify top hotspots before making changes.

Frequently Asked Questions about openclaw-test-performance

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

FAQPage Schema

How do I identify bottlenecks in my vitest test suite?▼

To identify bottlenecks in a vitest test suite, run structured benchmarking and hotspot analysis to quantify import delays, CPU load, and memory pressure, establishing a performance baseline to target specific optimizations.

What is the best way to reduce RSS memory pressure during pnpm test runs?▼

Reducing RSS memory pressure during pnpm test runs involves profiling memory footprints to locate inefficient tests and large allocations, then applying guided optimizations to lower memory usage while preserving coverage and reliability.

How do I profile CPU hotspots and slow coverage paths in vitest?▼

Profiling CPU hotspots and slow coverage paths in vitest requires using diagnostic tooling to measure test execution times and coverage overhead, helping you pinpoint inefficient tests and propose repeatable steps for acceleration.

Does this benchmarking workflow support scoped subsets of the test suite?▼

Yes, the benchmarking workflow supports scoped subsets of the test suite, allowing you to run baseline measurements, hotspot analysis, and profiling on specific subsystems rather than only the entire test suite.

Why does my OpenClaw test suite take so long to run?▼

Your OpenClaw test suite may run slowly due to import hotspots, inefficient tests, or large memory footprints causing CPU and RSS pressure, which requires baseline measurement and targeted profiling to diagnose.