-
Notifications
You must be signed in to change notification settings - Fork 10
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
Problem: Sidekiq queues are not optimized for high volume federation #484
Comments
I'm curious about how the queues get stuck but have also run across this splitting idea, probably from the same post. |
In our case, the problematic one is At the moment, I have improved it by splitting the queues into:
Although performing better, this is still not optimal, it gets stuck from time to time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sidekiq queues usually get stuck due to the large amount of requests when federating. To scale up the server it is often necessary to split the different queues, as proposed here.
Proposed solution:
To split sideqik into different processes for
default
,push
,pull
,mailers
,scheduler
.Additionally, in more recent versions of mastodon an
ingress
queue has been implemented to handle toots from other instances. Perhaps that might help to optimize the traffic.The text was updated successfully, but these errors were encountered: