Skip to content

docs(tuning): vector bulk load & compaction guide + fix stray CHANGELOG marker#246

Merged
pilotspacex-byte merged 1 commit into
mainfrom
docs/tuning-vector-compaction
Jul 8, 2026
Merged

docs(tuning): vector bulk load & compaction guide + fix stray CHANGELOG marker#246
pilotspacex-byte merged 1 commit into
mainfrom
docs/tuning-vector-compaction

Conversation

@pilotspacex-byte

Copy link
Copy Markdown
Contributor

Adds a Vector bulk load and compaction section to docs/guides/tuning.md — operator guidance for the parallel-HNSW-build + insert-path-compaction work shipped in #237:

  • vectors are searchable immediately on the brute tier; the HNSW build now overlaps ingest across cores
  • COMPACT_THRESHOLD as the time-to-serve vs recall lever (streaming vs one-shot-bulk-load recipes)
  • MOON_VEC_COMPACT_WORKERS pool sizing + the ~10K-vector parallel-build threshold
  • per-shard bulk-load parallelism and the ingest-rate / recall trade-offs

Also fixes a stray <<<<<<< HEAD conflict marker that #237's squash merge accidentally left in the CHANGELOG [Unreleased] heading (the resolution dropped the =======/>>>>>>> lines but not the <<<<<<< line; the verify grep was $-anchored and missed the HEAD suffix).

Docs-only; no code paths touched.

…ELOG marker

Adds a "Vector bulk load and compaction" section to docs/guides/tuning.md
documenting the parallel-HNSW-build + insert-path-compaction behavior
shipped in #237: vectors searchable immediately on the brute tier, HNSW
build now overlapping ingest across cores, COMPACT_THRESHOLD as the
time-to-serve vs recall lever, the MOON_VEC_COMPACT_WORKERS pool knob, the
~10K-vector parallel-build threshold, per-shard bulk-load parallelism, and
the ingest-rate/recall trade-offs.

Also removes a stray `<<<<<<< HEAD` conflict marker that #237's squash
merge accidentally left in the CHANGELOG [Unreleased] heading — the merge
resolution dropped the =======/>>>>>>> lines but not the <<<<<<< line,
and the verification grep was $-anchored so it missed the trailing
" HEAD".

author: Tin Dang
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@pilotspacex-byte, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 24 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 258a2faa-9be0-4b58-95f0-740ea927d1d3

📥 Commits

Reviewing files that changed from the base of the PR and between ab41673 and 17f320a.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • docs/guides/tuning.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/tuning-vector-compaction

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@pilotspacex-byte pilotspacex-byte merged commit b36b862 into main Jul 8, 2026
9 checks passed
@TinDang97 TinDang97 deleted the docs/tuning-vector-compaction branch July 8, 2026 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants