Here are the DigitalOcean graphs for mastodon.technology over the past 7 days, and the past 24 hours. Yesterday required us to rebalance our resource utilization (before this week, we were over-provisioned and were preparing to decrease server resources to save costs 😅).

I think we're in an okay spot. We don't have a lot of headroom left. Fingers crossed today. We may need to close new registrations, but we'll be upfront if we make that decision.

Along with myself, this instance is moderated by @bclindner and @fuzzface – I'm fortunate to have such a great team 🙌

This instance is funded by a Patreon – if you'd like to contribute, head over to https://www.patreon.com/ashfurrow

One year ago, this instance was running on Docker. This configuration had been officially supported, but discouraged, by Mastodon maintainers – and for good reason. It introduced so many problems and so much overhead that I'm really grateful that everyone peer-pressured me into migrating off it. Now it runs as standard linux services. I'm positive this instance would be in tears right now, otherwise 😆

Sidekiq queues have continued to get worse. (But at a slower rate! Yes!!!) I’ve played with the config of everything as much as I’m comfortable – a sluggish instance is better than an unresponsive instance.

43k jobs queued up. default has a latency of 22 minutes, pull is over two hours lol okay

I see a few jobs taking a long time (>10 minutes) but most finish instantly. I’m trying to figure out where the next bottleneck to scale up is. How do I get the CPU cores doing more? PgBouncer? Multiple Sidekiq services? It seems like I have CPU headroom, so should I get more aggressive with my Postgres config? Is there a quick win without prolonged downtime? These are the questions on my mind.