Conversation

Notices

1. Embed this notice
   esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Sunday, 29-Dec-2024 02:02:29 JST esmevane, sorry

   • Masto.host

   @mastohost Hey there! I'm trying to navigate the new web interface (which is really nice, btw! good work). It looks like my DB is HUGE for some reason, 5.18gb. Is there anything I can do on my end to cut that down? There's only like 2 active folks on my instance, so I'm hoping most of that is unnecessary stuff we can do without

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Sunday, 29-Dec-2024 02:32:46 JST esmevane, sorry

     in reply to

     • Masto.host

     @mastohost Gotcha! So - if I've pulled a backup, it's "safe" to do this in the sense that I have a copy, but unsafe in the sense that the live instance will lose access to those old posts?

   • Embed this notice
     Masto.host (mastohost@mastodon.social)'s status on Sunday, 29-Dec-2024 02:32:47 JST Masto.host

     in reply to

     @ironchamber Hello! The work in the web interface and every update is done by the Mastodon dev team, not me. But really glad you like it.

     Regarding the database size, the number of local users is not a good deterministic on the storage usage. If you start a new server and follow 200 remote accounts and then never go back to the server, the storage will grow and grow endlessly because every post from those 200 remote accounts will be stored/cached locally.

   • Embed this notice
     Masto.host (mastohost@mastodon.social)'s status on Sunday, 29-Dec-2024 02:32:47 JST Masto.host

     in reply to

     @ironchamber The easiest way to reduce the database size is to set a 'Content cache retention period', that has consequences like I explain here https://masto.host/mastodon-content-retention-settings/ but that can slow down the growth and even reduce the database size, depending on what you set it to.

     Feel free to reach out if you have any questions or if there is something I can help with.

   • Embed this notice
     Masto.host (mastohost@mastodon.social)'s status on Sunday, 29-Dec-2024 02:54:54 JST Masto.host

     in reply to

     @ironchamber Regarding being safe, it's safe to set a 'Content cache retention period' as long as you are OK with the consequences of losing all cached posts from remote users older than the time you set in there. That signifies that if you favorited, boosted, bookmarked, received a reply from a user that is remote and that is older than that time, that will be lost and unrecoverable.

   • Embed this notice
     esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Sunday, 29-Dec-2024 02:54:54 JST esmevane, sorry

     in reply to

     • Masto.host

     @mastohost Ok! Thanks for the info. It sounds like it might be safest to bump up a tier for now and talk to all my users before doing any changes here.

   • Embed this notice
     Masto.host (mastohost@mastodon.social)'s status on Sunday, 29-Dec-2024 02:54:55 JST Masto.host

     in reply to

     @ironchamber Well, the backup will only be useful in a last case scenario. There is no easy way to restore it without losing all federation since the backup was generated until the restore happens.