-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialization of IVF Flat and IVF PQ #919
Serialization of IVF Flat and IVF PQ #919
Conversation
2195740
to
c13a23f
Compare
c13a23f
to
e6aa1be
Compare
e6aa1be
to
db91e6e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this PR is still in draft and you intend to do more work on it to prepare it for merging but I wanted to provide a first-pass review just to help nudge it along.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cjnolet for the review! I have addressed the issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM, thanks @tfeher!
@gpucibot merge |
rerun tests |
This PR implements serialization to file for
ivf_pq::index
andivf_flat::index
structures.Index building takes time, therefore downstream projects (like cuML) want to save the index (rapidsai/cuml#4743). But downstream project should not depend on the implementation details of the index, therefore RAFT provides methods to serialize and deserialize the index.
This is still experimental:
Python wrappers are provided for IVF-PQ to save/load the index.