Just realized maybe some instance admins haven't seen this page, but I *did* describe how exactly Mastodon can be tuned: https://github.com/tootsuite/mastodon/blob/master/docs/Running-Mastodon/Tuning.md
The tips & tricks I wanted to write about when I have time are specific hardware / deployment decisions; but general principles *are* already described in that documentation page

@Gargron Mastodon uses Paperclip for managing media attachments, and Paperclip itself does the resizing/processing/etc right?

If so, to move media processing off-server would require an update to Paperclip itself?

@wogan It is technically possible to make thumbnail generation be a background job
@Gargron That wouldn't reduce the resource requirement though. It would be great to hook in a system like Cloudinary - push raw file, get back CDN links, with all the hard transcoding work taking place off-server.
@Gargron what is the server of mastodon.social?
@gargron Thanks. This is currently relevant to my life. :) cc: @TheMysteriousEm

@Gargron I found that really useful, though I'd love it if someone could add more detail for new admins with little context. I had to experiment a bit to get everything right, and lean on programming knowledge to make educated guesses at more-workers v more-threads-per-worker -- not all admins have that.

I considered a PR, but I'm still guessing/experimenting so I'd like to see a more experienced Masto admin write it.