Replying to
@jan@toot.io
@jan@toot.io @getajobmike@ruby.social 364M happy customers served.
Remote
Evan Phoenix
@evanphx@ruby.social
Bio-electric pattern matching meat
0
Followers
0
Following
15
Posts
Joined October 30, 2022
Posts
Replying to
@rstockm@chaos.social
@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.
Replying to
@thomasfricke@chaos.social
@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!
Replying to
@thomasfricke@chaos.social
@thomasfricke@chaos.social Ah yes! I got wind this was going to happen, wonderful!
Replying to
@renchap@oisaur.com
@renchap@oisaur.com Sure, I'm not currently a patreon so I don't have access, but definitely happy to jump on and help!
Replying to
@leah@chaos.social
@leah@chaos.social Yeah, the core count vs memory definitely impacts the math. Did you find a happy balance? What was it?
Replying to
@JohanEmpa@mastodon.green
@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.
Replying to
@pieceofthepie@social.n8e.dev
@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.
Replying to
@evanphx@ruby.social
@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.
Replying to
@mwp@nodots.xyz
@mwp@nodots.xyz @getajobmike@ruby.social Yup! Not being in cluster mode will save a small amount of memory as well.
Replying to
@getajobmike@ruby.social
@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.
Replying to
@jolvera@mas.pub
@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.
Replying to
@evanphx@ruby.social
@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!
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!)