Optimize benchmark execution and reset evaluation baseline - #28
Merged
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
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.
Summary
Motivation
Full benchmark runs were repeatedly rebuilding embeddings and indexes, making indexing unnecessarily slow and costly. Previous results also predated the corrected split and execution behavior and could no longer serve as a valid comparison baseline.
Redis was not introduced because it would not directly replace the current pgvector and OpenSearch responsibilities. Persistent embedding caching and safe index reuse provide the immediate performance improvement without changing the storage architecture.
Validation
git diff --checkpassedOperational notes
make bench-liveuses the canonical Gemini embedding configurationmake bench-live-localuses local Qwen embeddingsembedding.device: cuda