Skip to content

Publish Cloud Dev capacity benchmark #121

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rmcdaniel merged 3 commits into from
Sep 4, 2026
Merged

Publish Cloud Dev capacity benchmark #121

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d4a3b5e
Publish Cloud Dev capacity benchmark
durable-workflow-ops Sep 4, 2026
cbf898a
Correct Cloud Dev benchmark headline
durable-workflow-ops Sep 4, 2026
d4d8d01
Use workflow actions for monthly comparison
durable-workflow-ops Sep 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions docs/polyglot/cloud-control-plane.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,6 +235,48 @@ and failover independently. A self-hosted Server cannot be registered with,
attached to, or used as the backing runtime for a Cloud namespace. Embedded
Laravel, self-hosted Server, and Cloud are separate deployment choices.

## Cloud Dev Capacity

Cloud Dev is an isolated, single-host managed runtime for development and
evaluation. Each provisioned space receives the same runtime shape used for
the measurement below:

| Resource | Cloud Dev |
| --- | --- |
| Runtime compute | 1 shared vCPU, 1 GB RAM |
| Durable storage included | 5 GB |
| Runtime services | Server, queue worker, scheduler, MySQL, and Redis |
| Network path | Direct, space-specific HTTPS ingress |
| Customer workers | Run in the customer's environment |
| Availability | No SLA; maintenance interruptions are allowed |
| Runtime price | $0.03/hour, measured by minute, capped at $20/month |
| Storage above 5 GB | $2/GB-month |

Cloud Dev was measured with [DW Standard Workflow
v1](https://github.com/durable-workflow/server/tree/main/benchmarks/capacity),
a fixed comparison workload consisting of one workflow start, one external
activity, and one workflow completion with defined 1 KiB Avro inputs and
results. The test used the provisioned 1-vCPU/1-GB runtime topology, current
stable Server and PHP SDK artifacts, one PHP worker process, two client slots,
a 30-second warmup, and a five-minute measurement window.

| Measured result | Value |
| --- | ---: |
| Offered and completed rate | 0.25 standard workflows/second |
| Completed workflows | 75 of 75 |
| Errors / throttled starts | 0 / 0 |
| Scheduling latency, p50 | 28.0 ms |
| Scheduling latency, p95 | 95.1 ms |
| Scheduling latency, p99 | 134.5 ms |
| Final workflow backlog | 0 |
| 30-day workflow actions | 1,296,000 |

This is a measured development baseline, not a universal conversion for every
workflow and not an SLA. Larger payloads, additional activities, timers,
signals, queries, replay-heavy histories, and customer worker latency change
capacity. Cloud billing remains based on provisioned runtime time and durable
storage, not workflow operations.

## Billing Usage API

Cloud Dev uses one isolated, single-host runtime cell for each provisioned Dev
Expand Down