spicypath

Inspect any profile. A fast, zero-build, offline profile inspector that runs in the browser. Drop in a profile and explore it as a flame graph, a timeline, a sandwich (caller/callee), or a radial view — with search, semantic color, auto-collapse, and profile diffing.

• No build, no dependencies. Plain ES modules and a single Canvas 2D renderer; open it and it runs. Nothing is uploaded — parsing happens locally.
• Reads common formats: folded/collapsed, pprof, OTLP Profiles, V8 .cpuprofile, speedscope (sampled + evented), perf script, Gecko (Firefox Profiler / samply), and JFR (JDK Flight Recorder). See docs/formats.md.
• Views: Timeline (flame chart) · Aggregated (flame graph) · Sandwich · Radial, plus a diff/comparison mode.

It inspects profiles you point it at. It is deliberately not a dashboard, not a Grafana panel plugin, and it does not own collection or storage — those are permanent non-goals.

Quickstart

Try it live: spicypath.intentius.workers.dev — a sample loads on start; drop a profile or ⌘K to open your own.

Or run it locally — serve the src/ directory and open it in a browser:

cd src
python3 -m http.server
# then open http://localhost:8000

A sample profile loads on start. Drag a profile onto the window (or use the file picker) to open your own; .gz is decompressed automatically.

Usage

• Switch views between Timeline, Aggregated, Sandwich, and Radial. Timeline is available only for profiles that carry per-sample timing.
• Search (regex) dims non-matching frames.
• Zoom by double-clicking a frame or span; Esc resets.
• Diff two profiles with compare — red marks regressions, blue improvements.
• Export the current profile as .speedscope.json, .folded, or an .svg snapshot.
• Open from a URL or a live source — beyond local files: ⌘K → Open from URL fetches any supported profile by URL, and Connect to a profile source pulls from a Go /debug/pprof endpoint or queries a Pyroscope / Parca backend (the live token refetches). CORS permitting.
• Metrics — in Timeline, attach metric tracks (CPU/RAM/…) locked to the time axis: hover a track to light the stack at that instant, hover a frame to band its span on the tracks, and brush a range to see which functions dominated that window.
• Source lines — drop your source files (or Load source files… in ⌘K) and a selected function's source shows with per-line weight and heat shading. Matched locally by file name; nothing is uploaded.
• Share a view — the URL captures view, mode, weight, search, and zoom; links to a bundled sample or a live /debug/pprof endpoint reopen the same profile (dropped local files can't be re-fetched, but the view settings still restore).

Documentation

📖 Documentation site — the docs, rendered with search and navigation.

• docs/architecture.md — the canonical data model and the rendering design principles.
• docs/formats.md — supported input/export formats and how to add a parser.
• CHANGELOG.md — what has shipped, by milestone.
• GitHub issues — planned and open work (the FG-NNN ids carry into issue titles).
• CONTRIBUTING.md — conventions and how to add a parser or view.

Development

The app lives in src/ (ES modules, no build step). The test harness lives in test/ and imports the same parser/renderer cores, run with Node (TypeScript type-stripping; Node 23.6+ runs the .ts entry points directly):

node test/run.ts          # data-model validation
node test/golden.ts       # parse → model → re-emit round-trips
node test/ingest-test.ts  # format detection + ingestion
node test/export-test.ts  # export → re-import stability
node test/diff-test.ts    # diff math
node test/otlp-test.ts    # pprof <-> OTLP lossless-edge proof
node test/metrics-window-test.ts # metric-brush windowed re-aggregation
node test/adapters-test.ts # remote source adapters (Pyroscope/Parca) vs a mock server
node test/parse-jfr-test.ts # JFR parser vs a JDK-generated recording (skips without a JDK)
node test/sandwich-test.ts # sandwich focal selection (incl. hub-less profiles)
node test/sourceline-test.ts # per-line weight aggregation (recursion-safe)
node test/bench.ts         # scale benchmark
node test/browser.ts      # real-Chrome interaction checks (CDP)

GitHub Actions CI runs the test suite (Node logic + real-Chrome browser checks + a JDK-generated JFR recording) on every push and PR.

Deployment

The app is a static site (src/) deployed to Cloudflare Workers Static Assets — wrangler.jsonc serves ./src with no build step. Deploys run via Cloudflare Workers Builds (git integration), not from CI. One-time setup:

1. Cloudflare dashboard → Workers & Pages → Create → Workers Builds → connect the INTENTIUS/spicypath repo.
2. Build command: (leave empty — zero-build). Deploy command: npx wrangler@4 deploy.
3. Every push to main then deploys automatically. Live at spicypath.intentius.workers.dev. No API token lives in GitHub. (A custom domain like spicypath.intentius.io would require moving the intentius.io zone to Cloudflare — its DNS is currently at the registrar pointing to GitHub Pages for the docs.)

License

MIT — see LICENSE. Prior-art acknowledgements are in CREDITS.md; bundled third-party assets and their licenses are in THIRD_PARTY.md.