oh I had no idea. I've been considering it as my choice for instance software against Mastodon. Not looking at Pleroma due to scalability and caching since we're interested in infrastructure to handle up to 500 users. Misskey seemed a lot more modern and simple afa dependencies vs. Mastodon.
an instance *capable of supporting a proposed maximum* of 500 users. my group already has like 130 people. if we're going to re-deploy and invest in the hardware + time to spin everything up then we want the overhead and capabilities to be able to reliably handle up to 500 active users. @neko
mastodon and misskey, yeah, from everything ive looked into. pleroma is great for single user instances and smaller instances but doesnt scale like the other two do @neko
mastodon can scale horizontally across multiple servers, has better caching, utilizes redis and compression, has good documentation, and is under active development.
Misskey is similar afaik but also has a fuckton of other features and nifty things like user drives but also at the cost of heavily heabily JS dependent.
Idk maybe @alex can shed some light onto this topic @getindor
Mastodon is built on tech that is inherently expensive to scale, but its architecture allows for scaling it pretty much infinitely if you can throw money at it.
Pleroma is built on a way better software stack and has potential to scale cheaply, but gets easily bottlenecked by the Postgres database.
we have 2 dell r630s to play with. Can you provide some information re the differences in scalability and how pleroma gets bottlenecked? @neko@getindor
20,000 users all hitting the Home timeline at once. Every request is an SQL query with different parameters and there’s no cache. Even though Elixir can handle a fuckton of http requests, the database can’t handle the load.
There’s no way to shard the database, and CockroachDB doesn’t work either. I tried all the easy solutions. What it needs is pregenerated timelines in a cache like Redis. That’s why Mastodon doesn’t have this problem.
奇诺
•neko
•奇诺
•neko
•奇诺
•do the thug shaker :getglehappy:
•奇诺
•neko
•do the thug shaker :getglehappy:
•that seems unlikely
奇诺
•neko
•奇诺
•Misskey is similar afaik but also has a fuckton of other features and nifty things like user drives but also at the cost of heavily heabily JS dependent.
Idk maybe @alex can shed some light onto this topic @getindor
Alex Gleason
•Pleroma is built on a way better software stack and has potential to scale cheaply, but gets easily bottlenecked by the Postgres database.
Alex Gleason
•The reason Misskey is bad is because it doesn’t work with Soapbox.
:pascal:
•>Good
Gonna be very difficult convincing the fedi of this
neko
•Alex Gleason
•Doughnut Lollipop 【記録係】:blobfoxgooglymlem:
•Alex Gleason
•neko
•Alex Gleason likes this.
Alex Gleason
•奇诺
•Alex Gleason
•There’s no way to shard the database, and CockroachDB doesn’t work either. I tried all the easy solutions. What it needs is pregenerated timelines in a cache like Redis. That’s why Mastodon doesn’t have this problem.
gme 🇺🇸🇺🇦🏳️⚧️🏳️🌈
•Alex Gleason
•