add PQ training benchmark #482
Merged
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.
Overview
In order to gauge for variance in PQ performance over various architectures we need to have a baseline measurement within jVector that captures the relative cost of training.
We need to have the number of vectors as an adjustable parameter which is harder to do on a static dataset without creating skewness in data distribution.
Changes
Testing
PQ training benchmark:
PQ vs FP distance benchmark:
PQ vs FP Index Construction: