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

Improve performance of follow recommendation scheduler #16159

Conversation

ClearlyClaire
Copy link
Contributor

@ClearlyClaire ClearlyClaire commented May 5, 2021

Express follow_recommendations in terms of account_summaries rather than accounts, integrate filters that are unconditionally used, and materialize the resulting view.

This should result in the bulk of the computation being performed only once instead of once per recommendation language.

On my single-user instance, this results in a ~×4 speedup.

Express follow_recommendations in terms of account_summaries rather than
accounts, integrate filters that are unconditionally used, and materialize
the resulting view.

This should result in the bulk of the computation being performed only once
instead of **once per recommendation language**.
@ClearlyClaire ClearlyClaire force-pushed the fixes/follow_recommendations_schedulers-performances branch from 5407275 to 785dd90 Compare May 5, 2021 19:44
@ClearlyClaire ClearlyClaire changed the title [WiP] Improve performance of follow recommendation scheduler Improve performance of follow recommendation scheduler May 5, 2021
@ClearlyClaire ClearlyClaire marked this pull request as ready for review May 5, 2021 19:45
@Gargron Gargron merged commit d9ae3db into mastodon:main May 5, 2021
chrisguida pushed a commit to Start9Labs/mastodon that referenced this pull request Feb 26, 2022
Express follow_recommendations in terms of account_summaries rather than
accounts, integrate filters that are unconditionally used, and materialize
the resulting view.

This should result in the bulk of the computation being performed only once
instead of **once per recommendation language**.
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.

2 participants