So I see two ways forward for the fediverse, either:
A. Mastodon has to be refactored / rewritten to use Ruby Fibers, the non-blocking concurrency feature for Ruby
OR
B. We have to switch to a different Fediverse software that is based on a more modern software development framework.
Personally I think B might be the best option, and my money is on GoToSocial!!
@forestjohnson is gotosocial provably better @ handling load? I assume so bcuz golang concurrency but I'd like to see comparisons. also I wonder if heavy parts of the masto stack could be rewritten in go & the rest left alone
There's a lot that I don't know.
GoToSocial has had some performance issues in the wild already, mostly related to missing indexes on database / non-optimize queries. That's typical for any new application and usually very easy to solve in a relational database.
The hardware requirement to federate George Takei's toots right now is surely massive -- think ThreadRipper.
GoToSocial will probably be able to achieve a similar result on a mere Raspberry Pi 4.
@forestjohnson dam golang do be performant! I read their readme and it looks amazing