docs: record 120-VU v1.0 Cloudflare baseline
Baseline: 120/120 SSE connections opened/closed, 0 errors, p95 event 1.03 s, p95 scenario 194 ms, presenter POST 82.69 ms, 2,760 events, 2,400 pings, 4m53s. Raw summary is git-ignored. Also confirm pulse.noelsabia.dev already serves Nuxt; no route switch is needed. /stage and /live remain 404 on v1.0 until v1.1 is applied.
This commit is contained in:
1 parent
b98a1bab42
commit
d72878f560
3 files changed
+23
-6
No files matched your search
@@ -52,9 +52,12 @@ hostname, and verification steps.
|
||||
- Gitea pull is proven: `gitea-regcred` exists and the hello pod pulled from
|
||||
`git.noelsabia.dev/noel/hello:gate1`; the Service returned HTTP 200.
|
||||
- Tunnel `pulsecast-gate1` is active with `pulse` and `api-pulse` routes.
|
||||
`pulse` still points at the temporary hello Service until the v1.1 cutover.
|
||||
The API hostname is `api-pulse.noelsabia.dev` because Universal SSL only
|
||||
covers `*.noelsabia.dev`.
|
||||
`pulse` already serves the v1.0 Nuxt app; no route switch remains. `/stage`
|
||||
and `/live` are v1.1 pages. The API hostname is
|
||||
`api-pulse.noelsabia.dev` because Universal SSL only covers
|
||||
`*.noelsabia.dev`.
|
||||
- The 120-VU v1.0 baseline passed: 120/120 connections, 0 errors, p95 event
|
||||
1.03 s, p95 scenario 194 ms. Results are in `docs/load-test.md`.
|
||||
- v1.1 images are built from the service `main` worktrees, locally checked,
|
||||
and pushed. The cluster still runs the previous v1.0 images until this branch
|
||||
is reviewed/merged and explicitly applied.
|
||||
|
||||
+8
-3
@@ -33,8 +33,13 @@ Re-check before trusting this snapshot:
|
||||
Open-Meteo, and `git.noelsabia.dev`.
|
||||
- **Tunnel active:** `pulsecast-gate1` has routes for `pulse.noelsabia.dev`
|
||||
and `api-pulse.noelsabia.dev`; `cloudflared` is `1/1` with four HTTP/2
|
||||
connections. `api-pulse` serves the deployed API; `pulse` still points at
|
||||
the temporary hello Service until the web cutover.
|
||||
connections. `pulse` already serves the v1.0 Nuxt app
|
||||
(`x-powered-by: Nuxt`), so **no Cloudflare route switch remains**.
|
||||
`/stage` and `/live` return 404 on v1.0; v1.1 adds them. `api-pulse` serves
|
||||
the deployed API.
|
||||
- **120-VU baseline passed:** 120/120 SSE connections opened/closed, 0
|
||||
connection errors, p95 event latency 1.03 s, p95 scenario latency 194 ms;
|
||||
see `docs/load-test.md`. This was against v1.0.
|
||||
- **DNS works:** public resolvers return Cloudflare IPs for
|
||||
`pulse.noelsabia.dev` and `api-pulse.noelsabia.dev`. A local
|
||||
`systemd-resolved` negative cache can be cleared with
|
||||
@@ -63,7 +68,7 @@ Re-check before trusting this snapshot:
|
||||
| Read-only cluster/manifest check | agent or human | **ready now** (`make gate1-check`) |
|
||||
| Gitea push login + hello-world push | human | **done**; hello pull and Service verified |
|
||||
| `gitea-regcred`, `cloudflared`, `control-auth` Secrets | human | **done** |
|
||||
| Cloudflare Tunnel + public hostnames/DNS | human | **done**; tunnel active; `pulse` still points at hello |
|
||||
| Cloudflare Tunnel + public hostnames/DNS | human | **done**; tunnel active; `pulse` serves Nuxt |
|
||||
| `api`, `ml`, `web` images | human | **v1.1 pushed**; local manifest-equivalent checks pass |
|
||||
| v1.1 apply + smoke + presenter k6 + drills | human | **blocked on branch review/merge** |
|
||||
|
||||
|
||||
@@ -108,8 +108,17 @@ Populate from the saved `k6/results/summary-*.json`; never estimate.
|
||||
|
||||
| Run | Date | Opened | Closed | Open success | p95 event | p95 scenario | Presenter success | Errors |
|
||||
|---|---|---|---|---|---|---|---|---|
|
||||
| v1.0 baseline through Cloudflare | 2026-11-14 08:07 CET | 120 | 120 | 100% | 1.03 s | 194 ms | 100% (82.69 ms) | 0 |
|
||||
| v1.1 through Cloudflare | pending post-merge run | | | | | | | |
|
||||
|
||||
Raw baseline result: `k6/results/summary-20261114T080747.json` (git-ignored).
|
||||
|
||||
Baseline details: 361/361 checks passed, 2,760 events received, 2,400
|
||||
heartbeat pings, 120 VUs, test duration 4m53s, presenter POST 82.69 ms.
|
||||
`p95 ping latency` was 1,045 ms. This run was against the live v1.0 API; rerun
|
||||
the same command after v1.1 is applied and replace the pending row with exact
|
||||
numbers.
|
||||
|
||||
## Notes
|
||||
|
||||
- `sse_event_latency` uses the server timestamp in `data.t` (ping) or `data.at`
|
||||
|
||||
Reference in new issue
Block a user