Skip to content

SVS Shared Thread Pool Refactor (MOD-9881)#925

Open
meiravgri wants to merge 1 commit intomainfrom
meiravg_adjustable_thpool
Open

SVS Shared Thread Pool Refactor (MOD-9881)#925
meiravgri wants to merge 1 commit intomainfrom
meiravg_adjustable_thpool

Conversation

@meiravgri
Copy link
Copy Markdown
Collaborator

@meiravgri meiravgri commented Mar 31, 2026

Step 1: Rename SVS thread pool internal methods to match shared pool terminology
Rename setNumThreads/getNumThreadssetParallelism/getParallelism and getThreadPoolCapacitygetPoolSize across VectorSimilarity. Public info API fields (numThreads, lastReservedThreads, NUM_THREADS, LAST_RESERVED_NUM_THREADS) remain unchanged. No behavioral changes.

Describe the changes in the pull request

A clear and concise description of what the PR is solving.

Which issues this PR fixes

  1. #...
  2. MOD...

Main objects this PR modified

  1. ...
  2. ...

Mark if applicable

  • This PR introduces API changes
  • This PR introduces serialization changes

Note

Low Risk
Low risk rename-only refactor that updates internal SVS/tiered SVS thread management method names and related assertions/tests, with no algorithm or data/serialization changes expected.

Overview
SVS thread-pool controls were renamed to match shared-pool terminology. getNumThreads/setNumThreads become getParallelism/setParallelism, and getThreadPoolCapacity becomes getPoolSize, including updated comments and assertions around single-vector vs bulk insert parallelism.

Tiered SVS background update/GC scheduling and benchmarks/unit tests were updated to use the new method names, while debug/info fields (e.g., numThreads, lastReservedThreads) remain unchanged.

Written by Cursor Bugbot for commit c78a851. This will update automatically on new commits. Configure here.

…l terminology**

Rename `setNumThreads`/`getNumThreads` → `setParallelism`/`getParallelism` and `getThreadPoolCapacity` → `getPoolSize` across VectorSimilarity. Public info API fields (`numThreads`, `lastReservedThreads`, `NUM_THREADS`, `LAST_RESERVED_NUM_THREADS`) remain unchanged. No behavioral changes.
@jit-ci
Copy link
Copy Markdown

jit-ci bot commented Mar 31, 2026

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 31, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.98%. Comparing base (f177c40) to head (c78a851).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #925   +/-   ##
=======================================
  Coverage   96.98%   96.98%           
=======================================
  Files         129      129           
  Lines        7574     7574           
=======================================
  Hits         7346     7346           
  Misses        228      228           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

1 participant