Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!
-
This issue is only just now slowly popping up around the few forums I frequent. This post won't give all the juicy details, but suffice to say you need to be sure you have LOTS of room on your VPS if you are running Mastodon. My impression of Cloudron users is that we use high-RAM but not necessarily high-storage VPSes. My own Mastodon instance has been running for just over a year. I opened it up to federate with other instances bit by bit over time. At first 1GB of RAM and just a few 10Gs of space was needed. But as I connected with more and more federated instances, connected with relays... my RAM and space requirement shot up. Right now it is a lowly connected instance - I follow only 128 users, and have 26 followers, and have just 2 pinned #s, and it now requires no less than 5.5GB of RAM. I had to switch to a new Minio instance 3 days ago (I forgot to renew my precious KS-1 on which it lived) and in THREE days it has 20GB stored in the new Minio bucket.
People, get ready.
A life lived in fear is a life half-lived
-
This issue is only just now slowly popping up around the few forums I frequent. This post won't give all the juicy details, but suffice to say you need to be sure you have LOTS of room on your VPS if you are running Mastodon. My impression of Cloudron users is that we use high-RAM but not necessarily high-storage VPSes. My own Mastodon instance has been running for just over a year. I opened it up to federate with other instances bit by bit over time. At first 1GB of RAM and just a few 10Gs of space was needed. But as I connected with more and more federated instances, connected with relays... my RAM and space requirement shot up. Right now it is a lowly connected instance - I follow only 128 users, and have 26 followers, and have just 2 pinned #s, and it now requires no less than 5.5GB of RAM. I had to switch to a new Minio instance 3 days ago (I forgot to renew my precious KS-1 on which it lived) and in THREE days it has 20GB stored in the new Minio bucket.
People, get ready.
-
This issue is only just now slowly popping up around the few forums I frequent. This post won't give all the juicy details, but suffice to say you need to be sure you have LOTS of room on your VPS if you are running Mastodon. My impression of Cloudron users is that we use high-RAM but not necessarily high-storage VPSes. My own Mastodon instance has been running for just over a year. I opened it up to federate with other instances bit by bit over time. At first 1GB of RAM and just a few 10Gs of space was needed. But as I connected with more and more federated instances, connected with relays... my RAM and space requirement shot up. Right now it is a lowly connected instance - I follow only 128 users, and have 26 followers, and have just 2 pinned #s, and it now requires no less than 5.5GB of RAM. I had to switch to a new Minio instance 3 days ago (I forgot to renew my precious KS-1 on which it lived) and in THREE days it has 20GB stored in the new Minio bucket.
People, get ready.
-
@scooke Maybe I misread, but you say this is for a personal instance with just you as a user or do you have a small community using your instance? If so, how many users?
@MikeHuntington Very similar to @doodlemania2 . It's just me and my instance STILL processes that much data. It's the federation-side which opens the doors to that much data. If I wasn't connected to relays, if I turned off federation, if I just posted for myself (but, that's missing the point of both Mastodon and federation/ActivityPub), then it would likely still consume less than a GB of RAM and have less than 20GB of data stored on it.
-
This issue is only just now slowly popping up around the few forums I frequent. This post won't give all the juicy details, but suffice to say you need to be sure you have LOTS of room on your VPS if you are running Mastodon. My impression of Cloudron users is that we use high-RAM but not necessarily high-storage VPSes. My own Mastodon instance has been running for just over a year. I opened it up to federate with other instances bit by bit over time. At first 1GB of RAM and just a few 10Gs of space was needed. But as I connected with more and more federated instances, connected with relays... my RAM and space requirement shot up. Right now it is a lowly connected instance - I follow only 128 users, and have 26 followers, and have just 2 pinned #s, and it now requires no less than 5.5GB of RAM. I had to switch to a new Minio instance 3 days ago (I forgot to renew my precious KS-1 on which it lived) and in THREE days it has 20GB stored in the new Minio bucket.
People, get ready.
-
@scooke Thanks for the report!
You think this would be doc worthy?@BrutalBirdie said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
You think this would be doc worthy?
Can't hurt to mention it somewhere in the docs (and maybe even during the install process) that once you (or other users) start following a few people, and with federation on (it is by default) Mastodon will quickly start taking up a A LOT of space.
I've not yet noticed the RAM side of things myself, but that's possibly just because as soon as I noticed the disk space had run out and I unfollowed everyone as soon as I got the server running again to buy myself a little time to migrate over to a server with more storage.
-
@BrutalBirdie said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
You think this would be doc worthy?
Can't hurt to mention it somewhere in the docs (and maybe even during the install process) that once you (or other users) start following a few people, and with federation on (it is by default) Mastodon will quickly start taking up a A LOT of space.
I've not yet noticed the RAM side of things myself, but that's possibly just because as soon as I noticed the disk space had run out and I unfollowed everyone as soon as I got the server running again to buy myself a little time to migrate over to a server with more storage.
There's also an option in Mastodon to purge remote media (pulled in with federation on). Not sure if that config option is in Cloudron, but that would help with space.
-
There's also an option in Mastodon to purge remote media (pulled in with federation on). Not sure if that config option is in Cloudron, but that would help with space.
@MikeHuntington currently the package runs that purging as a cronjob: https://git.cloudron.io/cloudron/mastodon-app/-/blob/master/cleanup.sh
Is that the trigger you had in mind?
-
@MikeHuntington currently the package runs that purging as a cronjob: https://git.cloudron.io/cloudron/mastodon-app/-/blob/master/cleanup.sh
Is that the trigger you had in mind?
@nebulon Yup that's it! Good to see it was already a scheduled task.
By the way, today my database filled up and I was no longer able to access my Mastodon app. (using Digital Ocean) I increased my droplet size, but that didn't seem to help as the database is in a docker image(?). Seems there wasn't a way to resize that image to use more space.
So my app is stuck is a state of database failing to connect because space is maxed out.
-
@nebulon Yup that's it! Good to see it was already a scheduled task.
By the way, today my database filled up and I was no longer able to access my Mastodon app. (using Digital Ocean) I increased my droplet size, but that didn't seem to help as the database is in a docker image(?). Seems there wasn't a way to resize that image to use more space.
So my app is stuck is a state of database failing to connect because space is maxed out.
@MikeHuntington databases are provided as services to the apps on Cloudron. They run in their own container. Did the database run out of disk space (by default those are stored in /home/yellowtent/...) or did it run out of memory? For the latter you can adjust the memory limit in the services view.
-
@MikeHuntington databases are provided as services to the apps on Cloudron. They run in their own container. Did the database run out of disk space (by default those are stored in /home/yellowtent/...) or did it run out of memory? For the latter you can adjust the memory limit in the services view.
-
@nebulon It ran out of diskspace after running mastodon for about 24 hours (with federation relays added)
@MikeHuntington in such cases go through the checklist at https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full
-
@MikeHuntington in such cases go through the checklist at https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full
@nebulon Thank you for that link! Is if possible to have my database run on a different server than the one cloudron is running on? Also is AWS S3 an option?
I know I can edit Mastodon's .env file directly but will Cloudron support that?
I think that'll help with diskspace a ton as well.
-
@nebulon Thank you for that link! Is if possible to have my database run on a different server than the one cloudron is running on? Also is AWS S3 an option?
I know I can edit Mastodon's .env file directly but will Cloudron support that?
I think that'll help with diskspace a ton as well.
@MikeHuntington If you check out Cloudron's Mastodon forum there are a few discussions about how to use software like S3, Minio, Object Storage. It will def work.
EDIT: I just restarted my Owncast instance and set it up to use my Minio instance in just a few minutes. Once you get your head around how it all works, it's super smooth and do-able. -
@MikeHuntington True, and eventually I'll implement those commands to run automatically, but I imagine that someone who is surprised and frustrated by a rapidly-filling-up server won't have the tech skills, inclination or time to run those regularly anyway.
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket (or there could be a drop-own menu offering S3, Scaleway or Minio), and also set the .env.production settings correctly. I realize doing that is relatively simple if you've done it before, but otherwise it could prove to be a barrier.
A life lived in fear is a life half-lived
-
@MikeHuntington True, and eventually I'll implement those commands to run automatically, but I imagine that someone who is surprised and frustrated by a rapidly-filling-up server won't have the tech skills, inclination or time to run those regularly anyway.
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket (or there could be a drop-own menu offering S3, Scaleway or Minio), and also set the .env.production settings correctly. I realize doing that is relatively simple if you've done it before, but otherwise it could prove to be a barrier.
-
rcloneis a swiss army tool for connecting/mounting to remote storage and more.So if you have a deep store in GDrive, B2, Scaleway, Dropbox, etc you can connect them to your apps data/cache dirs.
@robi said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
rcloneis a swiss army tool for connecting/mounting to remote storage and more.So if you have a deep store in GDrive, B2, Scaleway, Dropbox, etc you can connect them to your apps data/cache dirs.
Thanks for this very sweet knowledge! rclone has a (currently experimental) GUI (Graphical User Interface) which appears in the web browser. If Cloudron try supporting this, I hope they make use of it.
There are some lovely things rclone can interact with, apparently. I notice that rclone can help with internet archive:
-
@MikeHuntington True, and eventually I'll implement those commands to run automatically, but I imagine that someone who is surprised and frustrated by a rapidly-filling-up server won't have the tech skills, inclination or time to run those regularly anyway.
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket (or there could be a drop-own menu offering S3, Scaleway or Minio), and also set the .env.production settings correctly. I realize doing that is relatively simple if you've done it before, but otherwise it could prove to be a barrier.
@scooke said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
@MikeHuntington True, and eventually I'll implement those commands to run automatically, but I imagine that someone who is surprised and frustrated by a rapidly-filling-up server won't have the tech skills, inclination or time to run those regularly anyway.
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket (or there could be a drop-own menu offering S3, Scaleway or Minio), and also set the .env.production settings correctly. I realize doing that is relatively simple if you've done it before, but otherwise it could prove to be a barrier.
This is a great idea and could remove a lot of friction for people wanting to self-host in the Fediverse.
-
@scooke said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
@MikeHuntington True, and eventually I'll implement those commands to run automatically, but I imagine that someone who is surprised and frustrated by a rapidly-filling-up server won't have the tech skills, inclination or time to run those regularly anyway.
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket (or there could be a drop-own menu offering S3, Scaleway or Minio), and also set the .env.production settings correctly. I realize doing that is relatively simple if you've done it before, but otherwise it could prove to be a barrier.
This is a great idea and could remove a lot of friction for people wanting to self-host in the Fediverse.
@LoudLemur said in Running a federated Mastodon instance will take up ALOT of space and RAM - be prepared!:
A win for Cloudron would be to offer a combined federation app - Mastodon + Scaleway, where the Mastodon instance also generates a user, Access Key ID and Secret Access Key which the user could then plug into a Scaleway Object Storage bucket
+1 I'm too scared to run Mastodon on my server due to it eating all the disk. This would help.
