feat: Implement mw_vu percentage-based thread allocation #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
EeshaaKhan
commented
Dec 15, 2025
EeshaaKhan
commented
- config.json: Added mw_vu parameter to test case configurations
- config/vectordb.xml: Updated mixed_workload section with default mw_vu
- src/postgresql/pgoltp.tcl: Add runtime calculation of OLTP/Vector thread split from mw_vu percentage
- pg_tproccv_diskann_run.py: Updated to use mw_vu percentage instead of hardcoded thread counts
- pg_tproccv_hnsw_run.py: Updated to use mw_vu percentage instead of hardcoded thread counts
- mixed_workload.py: set mw_vu from config before loadscript
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.