You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(bench): emit v3 JSONL records and dual-write to bench server
Brings the v3 emitter and CI dual-write plumbing from ct/benchmarks-v3
onto develop without the v3 server/website code. CI continues to write
v2 results to S3 unchanged; v3 ingest is gated on vars.V3_INGEST_URL
and `continue-on-error: true`, so when the variable is unset (or the
server is unreachable) the workflow no-ops.
vortex-bench:
- New `vortex-bench/src/v3.rs` with one record per `kind`
(`query_measurement`, `compression_time`, `compression_size`,
`random_access_time`, `vector_search_run`) plus a serde-tagged
`V3Record` enum, JSONL writer, and snapshot tests.
- `Dataset::v3_dataset_dims()` (default `(name(), None)`) lets
Public-BI map to `(public-bi, <subset>)`.
- `compress`/`runner` capture per-iteration timings and provide
`SqlBenchmarkRunner::v3_records()`.
Benchmark binaries (`compress-bench`, `datafusion-bench`,
`duckdb-bench`, `lance-bench`, `random-access-bench`,
`vector-search-bench`) gain `--gh-json-v3 <path>` for JSONL emission
alongside the existing `gh-json` flow.
bench-orchestrator passes `--gh-json-v3` through `vx-bench run`.
`scripts/post-ingest.py` reads JSONL, fills the `commit` envelope
from `git show`, wraps in `{run_meta, commit, records}`, and POSTs
to `/api/ingest`. Stdlib only.
Workflows:
- `.github/workflows/bench.yml` and `sql-benchmarks.yml` add
`--gh-json-v3 results.v3.jsonl` and a follow-up "Ingest results to
v3 server" step.
- New `.github/workflows/v3-commit-metadata.yml` POSTs an empty
envelope on every push to `develop` so the v3 `commits` dim stays
populated.
Files intentionally NOT brought over: anything under
`benchmarks-website/`, the workspace member additions for the
v3 server, and workflows depending on the v3 server crate. The v3
website ships in a follow-up PR off `ct/benchmarks-v3` once
dual-write is healthy in production.
Signed-off-by: Claude <noreply@anthropic.com>
0 commit comments