Recent searches
Search options
@m @aral @mastohost Mastohost probably has a lot more experience than me, but from what I've seen, I've been able to keep it from getting too crazy by at least keeping the push, pull, and ingress separated and giving them each a decent sized group of threads (25 for my instance) to work with. You also need to watch because they also need a DB connection for each thread, so DB POOL should match threads, and they should be under the max pool size for pgsql.
@mikey @m @aral Yep, Aral has a lot of followers and also is following a large number of people.
His plan has a limit of 12 Sidekiq threads. So, no matter the tuning, only 12 concurrent jobs can be active at the same time and with the large numbers of followers/following/activity more threads would be best but that would make the cost of hosting for a single user instance hosting even more expensive.
@mastohost wouldn't that be 24 sidekiq threads or do I not understand your pricing?
@aral
@jonah It's 24 Processing Threads. Like it say in the Pricing page https://masto.host/pricing/ under 'about the plans->Processing Threads':
"Example: If your plan has a limit of 4 Processing Threads. Your server can only perform 2 concurrent federation jobs and 2 concurrent short-lived HTTP requests simultaneously." Meaning on that example, you would get 2 threads for Sidekiq and 2 for Web.
