
Performance Investigation
- 111 installs
- 87.9k repo stars
- Updated August 2, 2026
- sveltejs/svelte
Helps with ai & agent building tasks.
About
performance-investigation is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- performance-investigation
- AI & Agent Building
- AI-coding skill
Performance Investigation by the numbers
- 111 all-time installs (skills.sh)
- +8 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #4,036 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/sveltejs/svelte --skill performance-investigationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 111 |
|---|---|
| repo stars | ★ 87.9k |
| Last updated | August 2, 2026 |
| Repository | sveltejs/svelte ↗ |
What it does
Helps with ai & agent building tasks.
Files
Quick start
1. Start from a branch you want to measure (for example foo). 2. Run:
pnpm bench:compare main fooIf you pass one branch, bench:compare automatically compares it to main.
Where outputs go
- Summary report:
benchmarking/compare/.results/report.txt - Raw benchmark numbers:
benchmarking/compare/.results/main.jsonbenchmarking/compare/.results/<your-branch>.json- CPU profiles (per benchmark, per branch):
benchmarking/compare/.profiles/main/*.cpuprofilebenchmarking/compare/.profiles/main/*.mdbenchmarking/compare/.profiles/<your-branch>/*.cpuprofilebenchmarking/compare/.profiles/<your-branch>/*.md
The .md files are generated summaries of the CPU profile and are usually the fastest way to inspect hotspots.
Suggested investigation flow
1. Open benchmarking/compare/.results/report.txt and identify largest regressions first. 2. For each high-delta benchmark, compare:
benchmarking/compare/.profiles/main/<benchmark>.mdbenchmarking/compare/.profiles/<branch>/<benchmark>.md
3. Look for changes in self/inclusive hotspot share in runtime internals (runtime.js, reactivity/batch.js, reactivity/deriveds.js, reactivity/sources.js). 4. Make one optimization change at a time, then re-run targeted benches before re-running full compare.
Fast benchmark loops
Run only selected reactivity benchmarks by substring:
pnpm bench kairo_mux kairo_deep kairo_broad kairo_triangle
pnpm bench repeated_deps sbench_create_signals mol_ownedTests to run after perf changes
Runtime reactivity regressions are most likely in runes runtime tests:
pnpm test runtime-runesHelpful script
For quick cpuprofile hotspot deltas between two branches:
node benchmarking/compare/profile-diff.mjs kairo_mux_owned main fooThis prints top function sample-share deltas for the selected benchmark.
Practical gotchas
bench:comparechecks out branches while running. Avoid uncommitted changes (or stash them) so branch switching is safe.- Each
bench:comparerun rewritesbenchmarking/compare/.resultsandbenchmarking/compare/.profiles.