vortex-data/vortex - CodSpeed

vortex

Blog Docs Changelog

Performance History

Latest Results

Use async_fs instead of LocalFileSystem in java bindings for local files Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/javalocalfs

41 minutes ago

fixes Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/pythonchanges

49 minutes ago

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

1 hour ago

Improve benchmark website hydration read path Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>

ct/many-connections

1 hour ago

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

3 hours 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

3 hours ago

Add `UnionVariants` type and embed it in `DType::Union` Replaces `DType::Union(Nullability)` with `DType::Union(UnionVariants, Nullability)`. `UnionVariants` carries a `FieldNames` list, per-variant `FieldDType`s, and an `i8` type-id vector (supporting non-consecutive tags like `[0, 5, 7]` so children can be removed without renumbering). The flatbuffer and protobuf `Union` schemas are extended with the `names`/`dtypes`/`type_ids` fields, and serde, flatbuffers, and protobuf paths are filled in with round-trip tests and nullability-constraint checks. All the `todo!()` stubs added in the previous commit for `DType::Union(..)` arms are left in place; concrete implementations land alongside the array work. Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>

ct/union-variants

3 hours ago

benchmarks-website/server: surface build SHA on /health + manual ops docs - build.rs runs `git rev-parse --short=12 HEAD` at compile time and exports VORTEX_BENCH_BUILD_SHA, with rerun-if-changed on .git/HEAD and .git/refs/heads so the SHA stays fresh across deploys. Falls back to "unknown" outside a git checkout. - HealthResponse grows a `build_sha` field (`&'static str`) and the /health handler populates it from env!(). Lets an operator run `curl /health | jq .build_sha` and compare against `cat /var/lib/vortex-bench/last-deployed-sha` to confirm the live process is the one the deploy timer last rolled out. - ops/README.md grows two sections under day-to-day: - "Which build is actually running?" — three identifiers, increasing levels of certainty. - "How do I manually rebuild and restart, outside the timer?" — three knobs (restart-only, force-deploy, manual checkout-and-build with the timer paused). Signed-off-by: Claude <noreply@anthropic.com>

ct/bench-v3-autopilot

3 hours ago

Latest Branches

0%

Use async_fs instead of LocalFileSystem in java bindings for local files#7904

9 hours ago

0907587

rk/javalocalfs

0%

Expose VortexSession in python bindings and switch to CurrentThreadRuntime#7896

50 minutes ago

aba4953

rk/pythonchanges

0%

Benchmarks Website V3: Admin and Auto-Deploy#7849

8 hours ago

02a5b97

ct/bench-v3-autopilot

© 2026 CodSpeed Technology

Home Terms Privacy Docs