performance investigation

AI Community

Skill notes

Quick start

Start from a branch you want to measure (for example foo). Run: If 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.json benchmarking/compare/.results/<your-branch>.json CPU profiles (per benchmark, per branch):

Suggested investigation flow

Open benchmarking/compare/.results/report.txt and identify largest regressions first. For each high-delta benchmark, compare: benchmarking/compare/.profiles/main/<benchmark>.md benchmarking/compare/.profiles/<branch>/<benchmark>.md Look for changes in self/inclusive hotspot share in runtime internals (runtime.js, reactivity/batch.js, reactivity/deriveds.js, reactivity/sources.js).

Fast benchmark loops

Run only selected reactivity benchmarks by substring:

Tests to run after perf changes

Runtime reactivity regressions are most likely in runes runtime tests:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@sveltejs · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview performance-investigation.preview
# Where outputs go

- Summary report: `benchmarking/compare/.results/report.txt`
- Raw benchmark numbers:
  - `benchmarking/compare/.results/main.json`
  - `benchmarking/compare/.results/<your-branch>.json`
- CPU profiles (per benchmark, per branch):
  - `benchmarking/compare/.profiles/main/*.cpuprofile`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.