Evan Phoenix

@jolvera@mas.pub 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.

@getajobmike@ruby.social For sure! Setting WEB_CONCURRENCY to cores * 1.5 can result in puma soaking up 100% of the cpu. So if you're running sidekiq on the same cores, use 1 * cores or even 0.8 * cores is prudent.

@rstockm@chaos.social @getajobmike@ruby.social Yeah, totally agree. I'm going to setup a google form to start gathering data now, that we could use for a calculator.

@jan@toot.io @getajobmike@ruby.social 364M happy customers served.

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

@JohanEmpa@mastodon.green I can't find one off hand atm. The quick answer is that you'll configure config/database.yml on the separate machine to point to the correct database, then when with new puma's started, you'll edit the nginx config to include the new machine's ip as a valid backend. Look for "rails cluster setup" guides, they should apply fine.

@jolvera@mas.pub So the official tips don't give concrete suggestions about how to tune puma. So it's still correct, just not specific enough!

@mwp@nodots.xyz @getajobmike@ruby.social Yup! Not being in cluster mode will save a small amount of memory as well.

@leah@chaos.social Yeah, the core count vs memory definitely impacts the math. Did you find a happy balance? What was it?

@thomasfricke@chaos.social @SheDrivesMobility@norden.social Sorry, don't know much of anything about mastodon the app itself, just happen to be versed in the rails architecture world!

@thomasfricke@chaos.social Ah yes! I got wind this was going to happen, wonderful!

@jolvera@mas.pub I’ll have to check!

@renchap@oisaur.com Sure, I'm not currently a patreon so I don't have access, but definitely happy to jump on and help!

@pieceofthepie@social.n8e.dev If puma is the only software running on the system, 1.5 * vCPU for WEB_CONCURRENCY is an easy place to start. If you're running sidekiq / nginx / postgres on the machine too, go for 0.8 * vCPU. Set MAX_THREADS to 16 and then see how it feels. You'll see a top end for the thread count, and then you'll know you need more WEB_CONCURRENCY or more raw cores.