feat: Add Custom Dataset support for Streaming Tests #2
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.
Summary
VectorDBBench supports custom datasets for performance tests (search-only benchmarks) but lacks support for custom datasets in streaming tests (concurrent insertion + search benchmarks). This prevents users from evaluating streaming performance on their domain-specific or proprietary datasets—a critical capability for production workload simulation.
This PR adds support for running streaming performance tests with custom datasets, following the same architectural pattern as custom performance tests.
Changes
StreamingPerformanceCaseto accept custom dataset configurationscase_typefield to differentiate streaming and performance datasets incustom_case.jsonNew Files
vectordb_bench/frontend/components/custom/displayCustomStreamingCase.pyModified Files
vectordb_bench/backend/cases.pyvectordb_bench/frontend/components/custom/getCustomConfig.pyvectordb_bench/frontend/config/dbCaseConfigs.pyvectordb_bench/frontend/components/run_test/caseSelector.pyvectordb_bench/frontend/pages/custom.pyvectordb_bench/custom/custom_case.jsonUser Workflow
/custompage/run_testpageTesting
Screenshots
[Add screenshots of the /custom page and /run_test page showing the new feature]