Skip to content
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

Periodically refresh the neighbourhood of matches #133

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

duogenesis
Copy link
Member

@duogenesis duogenesis commented Nov 19, 2023

Currently, the /search?n=${n}&o=${o} endpoint computes a globally optimal best match. It puts the top-500 globally optimal matches' personality vectors into search_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.

@duogenesis duogenesis changed the title Refresh the neighbourhood of matches Periodically refresh the neighbourhood of matches Nov 20, 2023
@duogenesis duogenesis force-pushed the refresh-match-neighbourhood branch from 0ec2237 to 904ad8f Compare November 20, 2023 13:38
@duogenesis duogenesis merged commit 4d8c60f into main Nov 20, 2023
1 check passed
@duogenesis duogenesis deleted the refresh-match-neighbourhood branch November 20, 2023 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant