Re:Scaling Mastodon in the Face of an Exodus
by sjustinas on Friday November 11, 2022 @02:48PM
(#33565835)
Just to note, Pleroma also uses a job queue: Oban. https://hexdocs.pm/oban/Oban.html
Re:Scaling Mastodon in the Face of an Exodus
by pmarreck on Friday November 11, 2022 @03:36PM
(#33566439)
Oban is great. (I subscribe to Oban Pro.) It's also seemingly very superior to Sidekiq-like solutions for job management.
But you don't need that. It's certainly a nice-to-have.
Re:Scaling Mastodon in the Face of an Exodus
by krainboltgreene on Friday November 11, 2022 @02:56PM
(#33565960)
> Well, that in short explains why Pleroma/Elixir is a much better stack to build this in
As someone who has extensive experience in both elixir and ruby, and mastodon itself, no this is doesn't.
Re:Scaling Mastodon in the Face of an Exodus
by pmarreck on Friday November 11, 2022 @03:39PM
(#33566490)
I read that a Pleroma instance can handle at least 10-50x the traffic of a Mastodon instance running on the same hardware. Based on the reports from other sites that have switched from Ruby to Elixir, this rings true. Are you claiming otherwise? I mean, the lack of a GIL alone (thank you, functional language with immutable data!) should give a pretty massive performance improvement
Well, that in short explains why Pleroma/Elixir is a much better stack to build this in. You don't need Sidekiq (https://sipsandbits.com/2020/08/07/do-we-need-background-job...) and you aren't stuck with a GIL (Global Interpreter Lock).