rsbuild-performance-profiling

Use when profiling, analyzing, reporting, or optimizing Rsbuild performance, including build, dev server, rebuild, static asset serving, memory usage, and CPU profile analysis.

Jump to install

Repository: web-infra-dev/rsbuild
Last source activity: June 22, 2026 at 02:48
Detected SKILL.md language: English
Stars: 3,364
Forks: 273

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/web-infra-dev/rsbuild --skill rsbuild-performance-profiling

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

create-draft-release-notes

Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable. Use for release notes, draft releases, release PR checks, npm staged publishing checks, and optional highlights.

2026-08-06

add-doc-anchor-ids

Align Rspress heading anchor IDs between English and Chinese docs. Use for MDX `\{#...}` anchors, shortened hashes, redundant anchors, or dead links.

2026-08-03

pr-creator

Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.

2026-07-23

View all from this repository

Rsbuild Performance Profiling

Workflow

Define the target scenario before collecting data:

operation: build, dev startup, rebuild, request serving, memory usage, or another explicit flow
benchmark project or fixture
metric: wall time, CPU time, self time, allocations, RSS, heap
success threshold, if the user provided one

Record the baseline first. Keep runtime, package manager, dependencies, environment variables, command flags, and input project unchanged for comparisons.

Save raw artifacts when available, such as CPU profiles, heap snapshots, logs, timing output, and benchmark commands. Do not rely only on subjective observations.

Separate costs by ownership:

Rsbuild code paths
Rspack or loader/plugin internals
third-party dependencies
user project code or benchmark fixture code

Rank findings by measured impact. Prefer self time for direct optimization targets and total time for understanding call-chain impact.

If implementing an optimization, keep behavior unchanged unless the user explicitly asked for a behavior change. Prefer small, measurable changes over broad refactors.

Re-run the same benchmark after changes. Report before/after numbers, absolute delta, percentage delta, and any variance or confidence limits you can observe.

Analysis Rules

Treat the user's supplied profiles, reports, and benchmark numbers as the source of truth for that task.

Do not claim a performance win without comparable before/after measurements.

Do not optimize generated output, dependencies, or benchmark fixture code unless the user asked for that scope.

For CPU profiles, call out both hot functions and why they are on the hot path.

For memory tasks, distinguish peak usage from stable usage after warmup or repeated rebuilds.

Output

Return a concise report with:

benchmark command or data source

top findings ordered by impact

Rsbuild-owned optimization opportunities

changes made, if any

validation results and remaining risk