59be60e1c3
Some checks failed
Veza CI / Backend (Go) (push) Failing after 4m55s
Veza CI / Rust (Stream Server) (push) Successful in 5m37s
Security Scan / Secret Scanning (gitleaks) (push) Failing after 1m16s
E2E Playwright / e2e (full) (push) Failing after 12m18s
Veza CI / Frontend (Web) (push) Failing after 15m31s
Veza CI / Notify on failure (push) Successful in 3s
End of W4. Capacity validation gate before launch : sustain 1650 VU
concurrent (100 upload + 500 streaming + 1000 browse + 50 checkout)
on staging without breaking p95 < 500 ms or error rate > 0.5 %.
Acceptance bar : 3 nuits consécutives green.
- scripts/loadtest/k6_mixed_scenarios.js : 4 parallel scenarios via
k6's executor=constant-vus. Per-scenario p95 thresholds layered on
top of the global gate so a single-flow regression doesn't get
masked. discardResponseBodies=true (memory pressure ; we assert
on status codes + latency, not payload). VU counts overridable via
UPLOAD_VUS / STREAM_VUS / BROWSE_VUS / CHECKOUT_VUS env vars for
local runs.
* upload : 100 VU, initiate + 10 × 1 MiB chunks (10 MiB tracks).
* streaming : 500 VU, master.m3u8 → 256k playlist → 4 .ts segments.
* browse : 1000 VU, mix 60% search / 30% list / 10% detail.
* checkout : 50 VU, list-products + POST orders (rejected at
validation — exercises auth + rate-limit + Redis state, doesn't
burn Hyperswitch sandbox quota).
- .github/workflows/loadtest.yml : Forgejo Actions nightly cron
02:30 UTC. workflow_dispatch lets the operator override duration
+ base_url for ad-hoc capacity drills. Pre-flight GET /api/v1/health
aborts before consuming runner time when staging is already down.
Artifacts : k6-summary.json (30d retention) + the script itself.
Step summary annotates p95/p99 + failed rate so the Action listing
shows the verdict at a glance.
- docs/PERFORMANCE_BASELINE.md §v1.0.9 W4 Day 20 : scenarios table,
thresholds, local-run command, operating notes (token rotation,
upload-scenario approximation, staging-only guard rail), Grafana
cross-reference, acceptance gate spelled out.
Acceptance (Day 20) : workflow file is valid YAML ; k6 script parses
clean (Node test acknowledges k6/* imports as runtime-provided, the
rest of the syntax checks). Real green-night accumulation requires
the workflow running on staging — that's a deployment milestone, not
a code change.
W4 verification gate progress : Lighthouse PWA / HLS ABR / faceted
search / HAProxy failover / k6 nightly capacity all wired ; W4 = done.
W5 (pentest interne + game day + canary + status page) up next.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| ci.yml | ||
| e2e.yml | ||
| go-fuzz.yml | ||
| loadtest.yml | ||
| security-scan.yml | ||
| trivy-fs.yml | ||