You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #12050 we added ability to reuse old graph as an initializer to speed up the merge, but even when we are re-inserting the old graph's node, we still need to calculate a similarity score here so that we can pop-out the worst non-diverse node here based on a sorted order.
But since the score is only used for diversity checking purpose, we probably do not even need them in some cases (like when we never reach the level connection limit). So we probably can first insert those nodes without calculating the score, then when we eventually need to pop out a worst node, we can calculate the score, sort the neighbor array and then do the normal "find the worst node" procedure.
The text was updated successfully, but these errors were encountered:
zhaih
changed the title
Lazily compute similarity score when reuse the old graph
Lazily compute similarity score when reuse the old HNSW graph
Apr 19, 2023
Jackyrie2
added a commit
to Jackyrie2/lucene
that referenced
this issue
Jun 14, 2023
Description
In #12050 we added ability to reuse old graph as an initializer to speed up the merge, but even when we are re-inserting the old graph's node, we still need to calculate a similarity score here so that we can pop-out the worst non-diverse node here based on a sorted order.
But since the score is only used for diversity checking purpose, we probably do not even need them in some cases (like when we never reach the level connection limit). So we probably can first insert those nodes without calculating the score, then when we eventually need to pop out a worst node, we can calculate the score, sort the neighbor array and then do the normal "find the worst node" procedure.
The text was updated successfully, but these errors were encountered: