vortex-data/vortex - CodSpeed

vortex

Blog Docs Changelog

Performance History

Latest Results

Lock file maintenance

renovate/lock-file-maintenance-python-lock-file-maintenance

5 hours ago

Lock file maintenance

renovate/lock-file-maintenance-js-lock-file-maintenance

5 hours ago

Lock file maintenance

renovate/lock-file-maintenance-rust-lock-file-maintenance

5 hours ago

Delete the Windows test outputs before the wheel build The first run of the merged Windows job passed all Rust tests, and then the wheel build failed with "There is not enough space on the disk". The wheel build cannot reuse target\ci, because it uses other RUSTFLAGS and target\x86_64-pc-windows-msvc, so delete target\ci first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018SWbErECNveeTkm1E4tBvp Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/ci-windows-single

19 hours ago

Run all Windows CI checks in one job Python (windows-x64) and Rust tests (windows-x64) each started their own Windows instance. A Windows instance takes 85-105s to boot cold, and the windows-x64-pre pool keeps only one hot instance, so the second job usually waited for a cold boot. The new Windows (x64) job runs the Rust tests and then builds and smoke-tests the wheel on one instance. The Rust test RUSTFLAGS and linker now apply only to the test step, so the wheel build is the same as before. The wheel steps also run when a Rust test fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018SWbErECNveeTkm1E4tBvp Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/ci-windows-single

20 hours ago

Run the amd64-ci-medium jobs from the stopped warm pool The stopped amd64-ci-medium pool (vortex-data/.github-private#47) has the same runner definition, image and s3-cache. A probe measured the job start at 11.0-15.3s from the pool against 14.6-14.7s for a cold launch. The first rustc -V took 0.4s against 1.4-2.8s, and the first cargo build 1.2s against 3.8-4.3s, because the pool disk is already read from its snapshot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018SWbErECNveeTkm1E4tBvp Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/ci-pool-medium

20 hours ago

Write file statistics in the legacy format for editions without aggregates Editions before the aggregates (for example core2025.10.0) do not permit `vortex.min`. The writer still wrote the nested statistics, but they were empty. Current readers and the write summary use the nested statistics when they are present, so they found no min, max or null count, although the legacy `field_stats` had them. When `vortex.min` is not permitted, write only the legacy `field_stats`. All readers then read them, and the write summary has them by the paths of the top-level fields. The check uses `vortex.min` and not "no aggregates", because a session can enable other families, such as spatial, that permit their own aggregates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Robert Kruszewski <github@robertk.io>

rk/jni-editions

1 day ago

Point the Ubuntu 26.04 CI image labels at the Ubuntu 26.04 AMIs (#11075) #10934 renamed the Linux CI image labels to `ubuntu26-full-{x64,arm64}-pre-v2`, but the `name` patterns in `.github/runs-on.yml` still match the old AMIs: | label | pattern before | AMI that CI boots | |---|---|---| | `ubuntu26-full-x64-pre-v2` | `vortex-ci-v2-x64-*` | `vortex-ci-v2-x64-20261030180912` (old cloud-init image) | | `ubuntu26-full-arm64-pre-v2` | `vortex-ci-v2-arm64-*` | old cloud-init image | The AMI build in `.github-private` now publishes `vortex-ci-v2-ubuntu26-{x64,arm64}-*`. This PR changes the patterns to match those names. Signed-off-by: Robert Kruszewski <github@robertk.io>

develop

1 day ago

Latest Branches

+3%

Lock file maintenance#11080

5 hours ago

d1db262

renovate/lock-file-maintenance-python-lock-file-maintenance

+13%

Lock file maintenance#11079

5 hours ago

f3b6c55

renovate/lock-file-maintenance-js-lock-file-maintenance

-2%

Lock file maintenance#11078

5 hours ago

aed5d2f

renovate/lock-file-maintenance-rust-lock-file-maintenance

© 2026 CodSpeed Technology

Home Terms Privacy Docs