Avatar for the vortex-data user
vortex-data
vortex
BlogDocsChangelog

Performance History

Latest Results

benchmarks-website/ops: restart.sh with visible before/after state `sudo systemctl restart vortex-bench-server` is silent on success, which is awful UX when you actually want to know the new process came up. Adds ops/restart.sh: snapshots the unit's MainPID + start time + symlink target + /health response, runs systemctl restart, waits up to 30s for the new process to answer /health, prints the same snapshot again, and exits 0/1 with a clear RESTART OK/FAILED line so the operator (or a script) doesn't have to guess. Sample output in the runbook section "How do I restart the server and *see* that it actually restarted?". Signed-off-by: Claude <noreply@anthropic.com>
ct/bench-v3-autopilot
6 minutes ago
benchmarks-website/ops: force-rebuild path for "redeploy current branch" The deploy timer's fast-path exit when `origin/$DEPLOY_BRANCH` hasn't moved is the right default — but it means there's no way to say "I want a fresh build of whatever's on the branch I'm tracking right now, even though origin hasn't moved." Real situations that hit this: - Flipped DEPLOY_BRANCH and want the new tip within seconds, not on the next commit there. - Edited /etc/vortex-bench.env in a way that needs a rebuild (build flags, target paths) rather than just a `systemctl restart`. - target/ got wedged and you want a clean rebuild from scratch. deploy.sh now accepts either `FORCE=1` in the environment or a `.force-rebuild` sentinel file under `$STATE_DIR`. Either path skips the stamp comparison so the full build → atomic swap → restart → /health cycle runs against `origin/$DEPLOY_BRANCH`. The sentinel is consumed on consumption so the very next ordinary timer tick is a normal no-op again. ops/force-rebuild.sh is a one-liner wrapper that drops the sentinel and triggers the deploy service — operator-facing, no env vars or systemd-override invocations to remember. ops/README.md grows a "How do I manually restart or redeploy?" section with three knobs in increasing order of work: restart-only, deploy-if-moved, and force-rebuild. Drops the earlier "manual cargo build from a local checkout" path which was over-documented; the force-rebuild + DEPLOY_BRANCH flip covers the same ground without encouraging hand-edited build state on the host. Signed-off-by: Claude <noreply@anthropic.com>
ct/bench-v3-autopilot
11 minutes ago

Latest Branches

CodSpeed Performance Gauge
0%
Benchmarks Website V3: Admin and Auto-Deploy#7849
5 hours ago
e45893d
ct/bench-v3-autopilot
CodSpeed Performance Gauge
+28%
4 hours ago
fce9864
ct/union-variants
CodSpeed Performance Gauge
0%
1 hour ago
9625ab4
ct/many-connections
Ā© 2026 CodSpeed Technology
Home Terms Privacy Docs