Scaling Mastodon in the Face of an Exodus

Re:Scaling Mastodon in the Face of an Exodus by mcguire on Friday November 11, 2022 @03:11PM (#33566153)

How much memory/cpu does Pleroma need for a single user instance?

[ Parent | on HN ]

Re:Scaling Mastodon in the Face of an Exodus by sjustinas on Friday November 11, 2022 @03:55PM (#33566698)

I spun up a test server of Pleroma recently. Following just a few people, 0 people following me AFAIK, I did join a few relays so my federated timeline is populated. It is currently showing 360MB RSS and the CPU load maxes out at ~50% of a single vCPU.

[ Parent | on HN ]

Re:Scaling Mastodon in the Face of an Exodus by self on Wednesday November 16, 2022 @01:05PM (#33627650)

I've run a single-user pleroma server since January 2019. I ran it on a digitalocean droplet with 2 GB RAM, and then an AWS instance (t3.small, also 2 GB) for the better part of two years; I recently switched to a t3.medium. Beam's current process size: 250MB resident, uses 5-7% CPU.

I discard remote posts after 120 days, and my database (using PostgreSQL 15, no RUM indexes) takes up just over 5.4 GB (as reported by `pg_database_size`). It's grown a lot faster in the past couple of weeks. I follow 245 accounts.

[ Parent | on HN ]