All checks were successful
Deploy Development / deploy (push) Successful in 41s
Test Suite / pytest-backend (push) Successful in 35s
Test Suite / lint-backend (push) Successful in 0s
Test Suite / build-frontend (push) Successful in 11s
Test Suite / playwright-tests (push) Successful in 57s
- Introduced a new section for the Performance-Baseline in CLAUDE.md and updated HANDOVER.md to include references to the new BASELINE_SNAPSHOT.md. - Enhanced architecture documentation in README.md to clarify the purpose of the baseline snapshot and its relevance to the refactor roadmap. - Refactored OrgInboxContext to implement a unified loading logic for join requests and content reports, improving code maintainability and performance. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
844 B
844 B
k6 – Health-Baseline (Phase 0)
Parallele GETs auf /health – ohne Auth, geeignet für Dev/Prod hinter dem gleichen Proxy wie die App.
Voraussetzung
Aufruf Beispiel
# Windows PowerShell
$env:BASE_URL="https://dev.shinkan.jinkendo.de"
k6 run scripts/load/k6-health-baseline.js
# Linux / macOS
```bash
BASE_URL=https://dev.shinkan.jinkendo.de k6 run scripts/load/k6-health-baseline.js
Wenn BASE_URL fehlt, nutzt das Skript die Default-URL im Script (anpassen bei Bedarf).
Auswertung
In der k6-Zusammenfassung http_req_duration → p(95) in BASELINE_SNAPSHOT.md eintragen.
Schwellwerte sind bewusst locker (p95 < 3s); bei Fehlschlag Proxy, Netz oder Backend prüfen.