Back to catalog / Developer tools
Workers profiling: optimize only after CPU or heap evidence
Confirm symptoms and deployed version, capture the right profile, and map it to source.
Skills
Read the production profiling guide and confirm account, Worker, environment, and deployed version. For a DO, confirm its Worker, namespace, and instance. Choose CPU or heap profiling by symptom. If cf CLI is absent, ask before installing; do not capture production data unapproved. Analyze pprof and report functions, source locations, units, and symbol gaps. Note missing source maps for generated JS. Propose the smallest evidence-backed fix and a same-workload retest; do not treat correlation as cause or modify live code automatically.
Permissions
Prerequisites
- Find CPU hotspots, latency causes, or allocation growth in deployed Workers or DOs.
Permissions
- Reads production profiles; confirm authorization for account and profiling access.
Limitations
Scope by account, Worker, env, version, and DO namespace; ground findings in profile evidence. No automatic fix/deploy.
Pinned upstream source
- Repository
- cloudflare/skills
- File path
- skills/workers-profiling/SKILL.md
- Pinned commit
53395984c3ea1925d00fce03b266112302f050e6- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Compatible tools
Cloudflare production profiling guide · cf CLI profile commands · Go pprof
Main topic
Take a coding Agent change from context to verification