Futureweb

Distributed Cloud

Cloudflare's Worker profiles are an October 9 post. InfoQ's account is October 23.

InfoQ said on October 23 that Cloudflare can profile Worker CPU and memory. The company's post is dated October 9. The docs require traffic already on the Worker.

The short version

Cloudflare's blog post is dated October 9, 2026. The docs, updated later in October, say a capture profiles a Worker or Durable Object that is already receiving traffic. A CPU profile shows time in functions. A heap profile samples allocations, and the docs say it is not a picture of memory still held. InfoQ's October 23 story is an account of that feature, not a second launch.

The wire date is not the blog date

The October 23 distributed-cloud wire carried InfoQ's headline that Cloudflare had brought on-demand CPU and memory profiling to production Workers. Cloudflare's own post, by Dominik Picheta, is dated October 9, 2026. The docs page says it was last updated October 20, 2026. A desk rail that sorts by the outlet's date will look like an October 23 launch. The documents say the announcement is two weeks older than the rail line, and the docs moved again on October 20. This brief files the feature against those clocks.the Korea certificate is a different Cloudflare document.

What a capture requires

The docs say the Worker or Durable Object needs traffic before and during the capture. The profiler attaches to an isolate that is already loaded. It does not send the request that would make the code run. Log filters and the time range in the historical view do not control the capture. The profile is the activity during the seconds you chose. A quiet script, profiled for ten seconds with nobody calling it, is an empty sample. That limit is the point of a production profile and also its blind spot.

CPU time is not retained memory

A CPU profile is the default, and it attributes processor time to functions. A heap profile, in the docs' words, collects a stack trace every 512 kilobytes allocated and records who allocated it. The docs say this is not whether that memory is still live. A wide frame on a heap flame graph is a lot of allocation during the window. It is not, by itself, a leak. Cloudflare's October 9 post says the same split in plainer language: CPU or memory, as a flame graph, from a Worker that has traffic. This page does not reprint the command the post uses to request a capture.a name is not where the machine sits.

Two Cloudflare pages, one InfoQ account

The blog introduces the dashboard path and a command-line path, and it says source maps matter if the Worker is TypeScript, or the names in the profile stay hard to read. The docs add the duration bounds, the heap sampling interval, and the warning that a heap profile is not a snapshot. InfoQ is the third source and the reason the item is on today's wire. InfoQ does not become a second invention of the feature. Where InfoQ and the docs disagree, the docs are the product description and InfoQ is the retelling.Workers are not the Korea audit.

What this is not

It is not a new region, and it is not a certificate. It does not move a customer's data. It lets the customer look at a slice of CPU time or of allocations on a Worker Cloudflare is already running. Local DevTools profiling, which the docs still describe separately, remains the tool for a breakpoint on a laptop. The October 9 claim is that the same kind of look can start against a production isolate. A production look still needs production traffic.on-device work is a different constraint.

Who can read the graph

The account that owns the Worker. A flame graph of someone else's script is not what the docs offer. Durable Objects are in the same sentence as Workers. A profile of a version requires that the version be the one receiving traffic. The docs say you pick latest or a version in the active deployment. An old version with no traffic is not a back-door into last month's logs.

Who is in scope

People running Workers or Durable Objects who need to know which function spent CPU time or allocated memory in a short window. People who wanted a launch dated October 23 are in scope only to be told the blog is October 9. People who do not run Workers are out of scope. The short answer this page will stand on is this: Cloudflare's blog post is dated October 9, 2026. The docs, updated later in October, say a capture profiles a Worker or Durable Object that is already receiving traffic. A CPU profile shows time in functions. A heap profile samples allocations, and the docs say it is not a picture of memory still held. InfoQ's October 23 story is an account of that feature, not a second launch.

What stays on the record

Blog: October 9, 2026, Dominik Picheta, on-demand CPU and memory profiles for Workers and Durable Objects, flame graph, traffic required. Docs: last updated October 20, 2026. CPU profile versus heap profile. Heap samples every 512 kilobytes allocated and is not retained memory. Duration 1,000 to 50,000 milliseconds. Capture does not invoke the Worker. InfoQ: October 23 account. Two of three sources are Cloudflare. Asked directly, Will a profile start a Worker that is idle? The docs say capture targets a recently active isolate and that capturing does not invoke the code for you. A Worker with no traffic in the window produces no useful profile. The historical log view does not choose what gets captured.

What would move the row

A Cloudflare note that changes the heap definition, or a docs change that lets a capture start an idle Worker, would be a later document. A second outside account that measured the overhead of a capture would be evidence this page does not have. Until then the record is the October 9 post, the October 20 docs, and InfoQ's later retelling. Asked directly, Did this ship on October 23? The blog date is October 9, 2026. InfoQ's piece is October 23. The wire line is the later account. The feature's clock is the blog and the docs.the advisory is the story.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. Cloudflare blog
  2. Cloudflare docs
  3. InfoQ

Questions

Did this ship on October 23?

The blog date is October 9, 2026. InfoQ's piece is October 23. The wire line is the later account. The feature's clock is the blog and the docs.

Will a profile start a Worker that is idle?

The docs say capture targets a recently active isolate and that capturing does not invoke the code for you. A Worker with no traffic in the window produces no useful profile. The historical log view does not choose what gets captured.

Is a heap profile a leak finder?

The docs say a heap profile records a stack every 512 kilobytes allocated during the capture. It measures allocations, not memory that remains. It is not a heap snapshot.

How long can a capture run?

The docs say the dashboard accepts a duration from 1,000 to 50,000 milliseconds, with a default of 10,000. That is a product limit, not a result.

Are the blog and the docs the same company?

Yes. InfoQ is the outside account. Two of the three sources are Cloudflare. This page says so.