Periodically refresh the neighbourhood of matches #133
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.
Currently, the
/search?n=${n}&o=${o}
endpoint computes a globally optimal best match. It puts the top-500 globally optimal matches' personality vectors intosearch_cache
. These personality vectors form a "neighbourhood" of the best match. Prior to this PR, for performance reasons, Q&A search computed a locally optimal new best match, only within this neighbourhood. This PR refreshes the neighbourhood sometimes---Not so much that Q&A search is slow and uses lots of CPU time, but not so little that users are unlikely to find their best match without refreshing the app.