CI: tier the test matrix into PR / main / nightly to cut Actions minutes
メンテナーはふだん 5 日以内に返信
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 32/100
調査の方向性
Start by reading the GitHub Actions workflow definitions and the referenced test and CMake configuration files, including tests/CMakeLists.txt and cmake/options.cmake. Compare each matrix entry with the coverage policy proposed in the issue, then agree on which jobs run for PRs, pushes to main, and nightly schedules. Done means the agreed tiers run the intended coverage and the per-push cost is reduced; the issue leaves that policy open for discussion.
索引モデルが issue の本文から書いたものです。
説明
The Intel OSPO flagged ScalableVectorSearch as using ~80k GitHub Actions minutes per month. Measured over 2026-09-16..10-16: 79.7k runner-minutes across 1,158 workflow runs. About 90% of that comes from pull_request events: each push to a PR runs ~25 jobs, and PRs average ~5 pushes.
This issue proposes splitting CI into tiers. Coverage policy is a team decision, so it is up for discussion here before any PR.
Where the minutes go
| Workflow | Minutes / 30d | Per green push |
|---|---|---|
| build-linux | 36.5k | 253 min (7 jobs) |
| build-linux-arm | 19.1k | 113 min (3 jobs) |
| build-cpp-runtime-bindings | 10.8k | 68 min |
| build-macos | 8.2k | 56 min |
| build-c-api-bindings | 3.3k | 22 min |
| cibuildwheel | 1.6k | 9 min |
The cost of a push went from 346 to 521 runner-minutes after #369 (2026-10-01).
What each matrix entry uniquely covers
-
ivf=OFF is a strict subset of ivf=ON. IVF only adds sources (
tests/CMakeLists.txtIVF lists,utils,benchmark) and the MKL link. Nothing ininclude/checksSVS_ENABLE_IVF. The build-without-MKL path is already covered by the clang-18 ASAN job, which is ivf=OFF. That makes the three RelWithDebInfo ivf=OFF jobs redundant. -
Compilers:
- There is almost no compiler-specific code (
meta.h:260,preprocessor.h:58/64). - g++-11 is the release toolchain; the LTO archive requires GCC 11.2.
- clang-15 is the oldest supported clang.
- clang-18 is ASAN.
- macOS clang-20 is libc++.
- g++-12 adds little, and builds with
-Wno-uninitialized(cmake/options.cmake).
- There is almost no compiler-specific code (
-
ARM has no NEON code, so it runs the generic kernels. Its unique value is the weak memory model for the concurrent index, and one compiler is enough to cover that. Today it runs three.
-
Not covered by any job today:
- the TSan targets (
SVS_EXPERIMENTAL_ENABLE_CONCURRENT_TSAN) - integration tests under ASAN (they are not compiled in Debug)
SVS_NO_AVX512=YES- NUMA
- the full-size concurrent stress tests, after #433
AVX-512 coverage depends on which runner a job lands on: 16 of the 26 sampled runners lacked AVX-512, and 14 of those were AMD EPYC 7763.
- the TSan targets (
Proposal
| Tier | Jobs | ≈ min per push |
|---|---|---|
| PR | x86 g++-11 ivf=ON (+ binaries and examples), x86 clang-18 ASAN ivf=OFF, ARM g++-12, cpp-runtime ×2, c-api ×2 + integration, cibuildwheel | ~150–180 |
| push to main | PR tier + clang-15 ivf=ON, g++-12 ivf=ON, macOS clang-20, FAISS integration | ~375 |
| nightly (schedule) | main tier + ARM g++-11 / clang-15, SVS_TEST_CONCURRENT_FULL_SIZE=ON, TSan targets, SVS_FORCE_INTEGRATION_TESTS under ASAN, SVS_NO_AVX512=YES, FAISS main HEAD |
n/a |
A failure that only the main or nightly tier can catch shows up after merge rather than before. Two ways to get that coverage before merge when it matters:
- a
full-cilabel that runs the main-push tier on a PR; - running macOS automatically when a PR touches platform-sensitive paths (allocator,
datatype.h).
The per-push minute figures are estimates computed from median job durations, not measurements.
Related
- #433: concurrent tests at small size by default. Measured: those tests take 107 s instead of ~550 s on 4 cores.
- #434: three flaky tests that cost ~2.8k min/month in failed jobs and reruns.
- #435:
paths-ignorefilters. Replayed on the last 30 days of PRs, they skip ~12k PR minutes. - Not in this issue, for separate follow-ups:
- prebuilt Docker image in GHCR (the image is rebuilt 8–9 times per push at 3.8 min each);
- pinning FAISS and caching its build;
- the static c-api variant failing on
mainsince 10-09 because of skew against the nightly LTO archive (see #387); - no required status checks are configured on
main.
- 主要言語
- C++
- スター
- 241
- フォーク
- 48
- 平均マージ
- 4日 21時間
- マージ済み PR（30日）
- 11
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
intel/ScalableVectorSearch のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
intel/ScalableVectorSearch#356 ·
メンテナーはふだん 5 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
intel/ScalableVectorSearch#469 ·
メンテナーはふだん 5 日以内に返信
-
enhancement
難易度 3/5 1〜2日 初心者へのやさしさ 32/100
intel/ScalableVectorSearch#460 ·
メンテナーはふだん 5 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 55/100
intel/ScalableVectorSearch#438 ·
メンテナーはふだん 5 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
intel/ScalableVectorSearch#427 ·
メンテナーはふだん 5 日以内に返信
intel/ScalableVectorSearch の issue をすべて見る
似ている issue
-
runtime: lf_f128_mod is documented as fmodq (truncating) but implements floor-based modulo; unusedオープンinternal correctness low priority rt_lib
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 87/100
-
PriorityNotificationQueue::wakeUpAll() loses the wake-up for a thread that is not waiting yet対応中かも @matejk が今日担当しました。 オープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
pocoproject/poco#5674 ·
メンテナーはふだん 2 日以内に返信
-
bug docs GUI
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
sonic-pi-net/sonic-pi#3609 ·
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
SanderMertens/flecs#2395 ·
メンテナーはふだん 1 日以内に返信