6 Commits

Author	SHA1	Message	Date
rob thijssen	d04f4ad704	feat(bench): show GPUs as the resource name instead of hostnames ... Public visitors don't know the hostnames, so surface each host's GPU(s) as the resource name across the UI. - store: gpu_label() turns the stored gpus_json into a compact label ("2× RTX 5090", "RTX 4090"); add `gpu` to ReportRow + RunRow and `host_gpus`/`model_gpus` maps to /api/dimensions (from each one's latest run). render_json gains gpu too. - UI: Overview + Runs show a "GPU" column (gpu, fallback host); Runs' filter is now GPU-labelled (still filters by host underneath); Trends shows a "Measured on <gpu>" line for the selected model. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 16:29:13 +03:00
rob thijssen	e3879f093a	feat(bench-ui): drop host selector from Trends; resolve host server-side ... Public visitors don't know the hostnames or per-host hardware, so the host picker on Trends was confusing. Select by model + scenario only; /api/series now takes host as optional and resolves it to the host serving that (model, scenario) — coherent since each model maps to one host today. Runs (drill-down) keeps its host filter. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 16:19:09 +03:00
rob thijssen	e4b9b88de0	feat(bench-ui): mark the baseline↔live regime boundary on Trends ... Add a dashed vertical ReferenceLine at the first live build (labelled "bench.py → helexa-bench") so the intentional gap between the gateway baseline and the direct-to-neuron series reads as a deliberate measurement-regime change, not missing data. The two series stay unconnected by design (different regimes, not directly comparable). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 16:13:34 +03:00
rob thijssen	21db334e37	feat(bench-ui): overlay pre-helexa-bench baseline on Trends ... Option C: a curated static baseline (bench/src/baseline.ts), transcribed from doc/benchmarks.md (8f6f1d3 + a1952a4 post-#11), overlaid on the Trends charts as a dashed, clearly-labelled historical series ahead of the bench era. Host inferred from model via the doc's fleet table; ordered by snapshot time so it anchors the timeline. Kept deliberately separate from the live series (no DB/API change) — the baseline is a different regime (bench.py through the cortex gateway, medians only) so it's never merged into the direct-to-neuron line; a caption spells out the distinction. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 16:02:43 +03:00
rob thijssen	37c19aa985	feat(bench-ui): public hosting at https://bench.helexa.ai via gateway nginx ... nginx on the gateway serves the bench SPA and reverse-proxies /api to the bob bench API over WireGuard — public, auth-less, same-origin (no CORS), internal API stays private. - asset/nginx/bench.helexa.ai.conf (full TLS vhost: SPA + /api proxy) and a bootstrap http-only vhost for the initial ACME challenge. - infra-setup.sh: one-time gateway setup — webroot, Let's Encrypt cert (certbot webroot, idempotent), install + enable the vhost. - deploy.yml: deploy-bench-ui builds the SPA (setup-node) and rsyncs dist/ to /var/www/bench.helexa.ai every deploy; built same-origin so no VITE_API_BASE. - cortex-host.conf: scoped gitea_ci rsync grant for the webroot. - bench/README: production hosting notes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 11:40:29 +03:00
rob thijssen	f50f5531cf	feat(bench): read-only JSON API on bob + bench/ React visualisation app ... Part A — helexa-bench read API: - [api] config (enabled, listen :13132); WAL on the store so API reads never block the sweep writer. - store read methods: summary, series (chronological per-build medians), runs (filtered), dimensions, run_count. - api.rs: axum /api/health|dimensions|summary|series|runs, permissive CORS (UI is a separate origin). The `run` daemon binds the API alongside the sweep; new `serve` subcommand serves API-only. - listener plumbing (bench gains a port): data/helexa-bench-firewalld.xml, spec install, deploy-bench /api/health probe + firewalld step, sudoers firewall-cmd grants, [api] in example + bob.toml. - 5 API tests + serve smoke. Part B — bench/ Vite + React-SWC-TS app (router, react-bootstrap, recharts): Overview (summary table), Trends (decode tok/s & TTFT across build SHAs), Runs (filterable explorer). Typed API client with VITE_API_BASE + dev proxy to bob. npm build/typecheck clean. Hosted separately from the API (per design); .gitignore excludes node_modules/dist. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-14 11:26:55 +03:00