3 ms·
32 cores and/or 128GB RAM - for how many concurrent users, 36.7k? It seems like Lemmy requires a fair bit of resources per user for a primarily text-based API,
by creamyhorror 3y ago
32 cores and/or 128GB RAM - for how many concurrent users, 36.7k? It seems like Lemmy requires a fair bit of resources per user for a primarily text-based API, more than I'd expected. Wonder where the majority of the resource burden lies - uncached local database queries? Too many simultaneous database connections?
- jochem9 3y agoFederation takes quite a toll. The way I read the article is that they didn't upgrade every time the load was (almost) too high, but instead opted immediately for the beefy dedicated server (considering the price it makes sense – it's on par with beefy VMs that have less power). They probably have resources to spare right now, but no need to go through the hassle of an upgrade soon (although 4 mins downtime sounds like they have things under control). Having said that, I'm sure there's plenty to improve in Lemmy, given it's used at a bigger scale now.
- spaduf 3y agoKeep in mind a lot of instances are preparing for what they anticipate to be the largest migratory wave yet when third party apps shut down at the end of the month.