[Workers] Add memory usage metrics changelog and docs#31695
Conversation
- Add changelog entry for memory usage visibility in Workers Metrics tab - Add Memory usage section to Workers observability metrics-and-analytics page - Add screenshot of Memory usage chart
Review⏸️ Automatic reviews for this PR are paused. This PR has already received 2 automatic reviews. To run another review, a codeowner can comment
✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. ✅ No code review issues found. Style Guide Review✅ No style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
- Remove broken link to DO metrics page from changelog - Rephrase 'per invocation' to 'at the time of each invocation' to avoid implying per-request allocation - Replace 'Learn more about' with 'Refer to' per style guide
|
|
||
| Memory usage metrics are also available for [Durable Objects](/durable-objects/observability/metrics-and-analytics/). | ||
|
|
||
| To view memory usage, go to **Workers & Pages**, select your Worker, and open the **Metrics** tab. You can also query memory usage programmatically via the [GraphQL Analytics API](/analytics/graphql-api/tutorials/querying-workers-metrics/) using the `workersInvocationsAdaptive` dataset — the `quantiles.memoryUsageBytesP50` through `quantiles.memoryUsageBytesP999` fields return percentile values in bytes. |
There was a problem hiding this comment.
What about for Durable Objects?
There was a problem hiding this comment.
the experience is almost the same except but on the DO page with 1 addition, @nevikashah can you also mention on the DO metrics tab you are able to filter by DO ID or Name so you can drill down and understand if that DO ran into issues because of memory?
|
|
||
|  | ||
|
|
||
| Memory usage measures the V8 [isolate](/workers/reference/how-workers-works/#isolates) memory at the time of each invocation. This is the same memory pool subject to the [128 MB per-isolate limit](/workers/platform/limits/#memory) — a single isolate can handle many concurrent requests and shares memory across them. |
There was a problem hiding this comment.
Can we not call this a "pool"? Similar in concept but not literally what this is?
There was a problem hiding this comment.
a single isolate can handle many concurrent requests and shares memory across them.
@iglesiasbrandon @vy-ton need to make sure we are explaining Durable Objects model here / somewhere / link to somewhere — to the extent reader needs to understand this in order to understand what the DO metric is or means
There was a problem hiding this comment.
@iglesiasbrandon worth you drafting section in DO docs to capture the DO memory model
|
|
||
| Memory usage metrics are also available for [Durable Objects](/durable-objects/observability/metrics-and-analytics/). | ||
|
|
||
| To view memory usage, go to **Workers & Pages**, select your Worker, and open the **Metrics** tab. You can also query memory usage programmatically via the [GraphQL Analytics API](/analytics/graphql-api/tutorials/querying-workers-metrics/) using the `workersInvocationsAdaptive` dataset — the `quantiles.memoryUsageBytesP50` through `quantiles.memoryUsageBytesP999` fields return percentile values in bytes. |
There was a problem hiding this comment.
the experience is almost the same except but on the DO page with 1 addition, @nevikashah can you also mention on the DO metrics tab you are able to filter by DO ID or Name so you can drill down and understand if that DO ran into issues because of memory?
|
We could also mention this in: /durable-objects/reference/in-memory-state/ |
- Add durable-objects to products frontmatter - Link to both Workers and Durable Objects in opening sentence - Remove 'pool' from memory description - Add DO-specific paragraph about in-memory state and hibernation - Replace viewing instructions with deep links and DO filter-by-ID mention - Update date to 2026-06-26 and rename files accordingly
|
@iglesiasbrandon just update the PR / make a PR that bases off this and suggests changes back into it |
What this PR does
Adds documentation for the new Memory Usage chart in Workers Observability Metrics tab.
Changes
Changelog entry (
src/content/changelog/workers/2026-06-25-memory-usage-metrics.mdx)Workers metrics docs (
src/content/docs/workers/observability/metrics-and-analytics.mdx)### Memory usagesection between Execution Duration and Invocation StatusesScreenshot (
src/assets/images/changelog/workers/observability/2026-06-25-memory-usage.png)Related
memoryUsageBytesandwasmMemoryBytesfields onworkersInvocationsAdaptive)