@phnt @NonPlayableClown @Owl @cvnt @dj @ins0mniak @transgrammaractivist

> The main problem is that lain likely never expected to Pleroma grow this large to instances with hundreds of users.

Well, sure, I made that remark in the linked-to thing:

> FSE is an edge case, but will not be forever. I think it is a good problem to have that scaling is becoming an issue, you don't wanna build super scalability into something that nobody ends up using, but it is the case that there are scaling issues that presently affect pleroma instances.

And that's November 2020.

> And that the developers don't run those active big instances.

I offered perf datasets many times. Server logs, Postgres logs. At the time that I wrote that post, there was a Prometheus endpoint that was open to the public on every single instance, so an interested party could collect performance data on every live Pleroma instance; it closed in the release immediately after that post.

I get it doesn't touch them and I get that the idea wasn't to run instances with this many users, but it's not number of users that introduce the scaling issues: it's number of activities.

> I don't remember what version FSE runs on (2.2.X I think),

It's modified and has fixes backported, but it is 2.2.2: http://demo.fedilist.com/instance/fsebugoutzone.org . (Still zero downtime! Everyone can suck my dick, I'm a goddamn genius hackerman.)

> You can still run Pleroma on cheap hardware, it just requires a lot of know-how in optimizing Postgres and Linux.

Well, a single-user one, following a few hundred people, I don't think you need much effort. At that level, concurrent users *do* start to matter.

> FluffyTail runs on BuyVMs $7 tier with the DB stored on a slab and it is yet to encounter a major performance issue after 1.5 years.

Oh, yeah, FSE started like that and I think we got to about a dozen people before I had to upgrade to whatever :francisco:'s next tier was.