History

Lars b06d026dd0 All checks were successful Deploy Development / deploy (push) Successful in 38s Details Test Suite / pytest-backend (push) Successful in 36s Details Test Suite / lint-backend (push) Successful in 0s Details Test Suite / build-frontend (push) Successful in 12s Details Test Suite / k6 /health Baseline (push) Successful in 33s Details Test Suite / playwright-tests (push) Successful in 57s Details chore(version): update version and changelog for release 0.8.118 - Bumped APP_VERSION to 0.8.118 and updated DB_SCHEMA_VERSION to 20260514062. - Enhanced the dashboard API with a new endpoint that consolidates training home data, allowing for a single request to retrieve upcoming training sessions, planned sessions with notes, and review pending items. - Updated the frontend Dashboard component to utilize the new API structure, improving data loading efficiency and user experience. - Added migration details and changelog entries to reflect the latest changes and improvements.		2026-05-14 08:53:09 +02:00
..
explain-readpaths.sql	chore(version): update version and changelog for release 0.8.118	2026-05-14 08:53:09 +02:00
k6-health-baseline.js	feat(docs): add performance baseline documentation and update architecture references	2026-05-14 06:53:37 +02:00
README.md	chore(version): update version and changelog for release 0.8.118	2026-05-14 08:53:09 +02:00

README.md

k6 – Health-Baseline (Phase 0)

Parallele GETs auf /health – ohne Auth, geeignet für Dev/Prod hinter dem gleichen Proxy wie die App.

CI / Deploy: In .gitea/workflows/test.yml eigener Job k6-health-baseline (nur Checkout + /health-Wartezeit + k6). Playwright läuft parallel/im selben Workflow im Job playwright-tests — ohne k6. Gleiche BASE_URL-Logik (Dev oder Prod nach workflow_run).

Voraussetzung

k6 installieren.

Aufruf Beispiel

# Windows PowerShell
$env:BASE_URL="https://dev.shinkan.jinkendo.de"
k6 run scripts/load/k6-health-baseline.js

# Linux / macOS
BASE_URL=https://dev.shinkan.jinkendo.de k6 run scripts/load/k6-health-baseline.js

Architektur: Der Workflow lädt linux-amd64 oder linux-arm64 je nach uname -m (z. B. Gitea-Runner auf Raspberry Pi 5).

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.

EXPLAIN (Phase 2)

Datei explain-readpaths.sql: Vorlagen für EXPLAIN (ANALYZE, BUFFERS) auf der Ziel-DB (manuell, nicht CI).