To all mastodon admins:

Hi! I’m Evan Phoenix, the primary author of puma, the ruby webserver that powers mastodon!

Please reply or DM me if you need tuning help! I’ve got no officiation with the mastodon, just want to see you succeed!

(Quick Tip: set WEB_CONCURRENCY to core count * 1.5 and then tune MAX_THREADS. High thread values will see diminishing returns!)

@evanphx i don't remember from the top of my head the tuning recommended in the mastodon doc, but that's what I followed, is what's there still valid and good advice?
@jolvera I’ll have to check!
@jolvera So the official tips don't give concrete suggestions about how to tune puma. So it's still correct, just not specific enough!
@evanphx is it worth doing a pull request to their doc to add the tunning you'd suggest?

@jolvera Yeah, probably! I want to figure out a way to gather some usage data from installations to provide even better info as well.

Also considering releasing a special puma-mastodon gem that will tweak these settings automatically.

@evanphx @jolvera Hi Evan, THANK YOU for Puma  
(here an admin of piaille.fr, a ~6000 users instance at the moment)

be careful that most instances have all services in one machine (postgresql, node, redis, elasticsearch, AND puma (AND sidekiq ;) )
so your automatic computation may not be right.
1.5* core count on a dedicated puma-only machine, sure ;)

@benjamin @jolvera Totes! As @getajobmike pointed out, gotta leave cpu headroom for others! 1 or 0.8 times core is safest.