Skip to content

Hub burst test ​

One-off load test for many sign-ups at once (#1521). It answers: if 5, 10 or 15 people sign up in the same minute, how long until the last hub is live, and what breaks first?

What it does ​

Actions → Hub burst test → Run workflow (count 1–15, default 15):

  1. Makes count new test home ids (e2e-burst-{stamp}-01 …).
  2. Puts a provision job for every one of them on the sandbox provision queue (lovely-home-hub-provision-sandbox) at the same moment. The sandbox hub-jobs Worker then dispatches the public orchestrator's Hub provision dispatch, exactly as for a real sign-up.
  3. Watches those runs and writes a table to the run summary: when each build started, when it went live (minutes after the jobs were queued), how long the build itself took, and how many runs failed and were retried.

There are no sign-ups, so it makes no Stripe customers. Each home gets a sandbox billing row first, like a real sign-up (the orchestrator refuses an e2e-* home without one, and reads the owner email from it): status active, owner E2E_OWNER_EMAIL, no Stripe subscription, and the "hub is live" and "build failed" emails marked as already sent, so the burst sends no email.

What to expect ​

The provision queue builds at most 4 homes at a time (max_concurrency in terraform/modules/platform_admin/queues.tf) and each build takes about 2.5 minutes, so homes go live in waves: about 3, 6, 9, 12 minutes … A failing build is retried after 30 s, up to 6 runs, and keeps its queue slot while it runs.

After going live each home records itself in platform/sites.yaml through the registry queue, one at a time on the VPS runner, so registry commits land on main for several minutes after the last home is live.

Afterwards: tear the homes down ​

The homes stay up. Run E2E sandbox cleanup with site_ids set to the comma list in the run summary and dry_run off. Wait until the registry commits for every burst home have landed first.

If nobody does, E2E stale hub sweep removes them once their registry record is 3+ hours old (see e2e-sandbox-cleanup.md).

What the first run found (2026-11-09) ​

At 4 builds at once, all 15 homes were live within 16 min. One hub upload and one platform-sandbox refresh hit Cloudflare's "creating deployments too quickly" limit. Pages deploys now wait and try again on that error (deploying.md, #1526).