-
Notifications
You must be signed in to change notification settings - Fork 107
Reduce device memory usage for CAGRA's graph optimization process (reverse graph creation) #832
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
base: branch-25.08
Are you sure you want to change the base?
Reduce device memory usage for CAGRA's graph optimization process (reverse graph creation) #832
Conversation
/ok to test bfc45cd |
/ok to test b0f648b |
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 Akira for the PR, looks good overall! Please find my comments below.
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
…rate functions and fix small issues
Thanks for the review Tamas, I think I've addressed everything you pointed out, could you double check? |
Since CAGRA improves search accuracy by merging forward and reverse graphs, reverse graph is created as part of the graph optimization process. Currently, GPU is used to create the reverse graph at high speed, but when creating a graph for huge dataset, the amount of device memory may be insufficient to create the graph.
In this PR, as a countermeasure for the lack of device memory, we will add an implementation in which reverse graphs are created on the CPU.