Introducing on-demand CPU and memory profiling with flamegraphs for Workers and Durable Objects
- ID
- 33623
- Status
- summarized
- Published
- 09 Oct 2026, 9:00 PM
- Fetched
- 09 Oct 2026, 10:28 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/workers-on-demand-profiling/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.0
- Created
- 09 Oct 2026, 10:29 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Cloudflare announced on-demand CPU and memory profiling for Workers and Durable Objects, viewable as interactive flamegraphs in the Observability page and downloadable for further analysis. You can start a profile via the CLI with `cf workers versions profile latest --worker-id "$WORKER_ID_OR_NAME" --duration-ms 5000 --profile-type cpu worker-cpu.pprof`, or from Build → Compute → Workers & Pages → Worker → Observability → Flamegraph. The profiler runs for a chosen duration against a selected Worker version, and Cloudflare says the Worker needs enough traffic for profiling to succeed.
Why it matters
If you run Workers or Durable Objects, you can now profile production traffic instead of guessing from logs and aggregate metrics; use a high-traffic version, run for a few seconds such as 5000 ms, and inspect the widest flamegraph functions or table view to decide what to optimize. TypeScript projects should enable source maps so the flamegraph maps back to your code.
Discussion angle
What production profiling signals would actually make you rewrite a Worker or Durable Object, and when is it cheaper to just scale up or add caching instead?