2/
Misskey and the Misskey forks (ex: Firefish, Sharkey, etc) seem to also be prone to their storage drives filling with:
• logs
• npm cache
• yarn cache
2/
Misskey and the Misskey forks (ex: Firefish, Sharkey, etc) seem to also be prone to their storage drives filling with:
• logs
• npm cache
• yarn cache
1/
RE: https://mastodon.social/@reiver/114019537398771505
The number one cause of Fediverse servers crashing seems to be the storage drives filling up with cached Fediverse user data — posts, profiles, avatar images, header images, etc.
But, Misskey and the Misskey forks (ex: Firefish, Sharkey, etc) also have an additional challenge that fills up their storage drives —
One thing about Akkoma that can cause you problems when hosting it is —
It stores media in the databases.
Including caching the profile images and profile headers from random people on the Fediverse.
This can cause your storage-drive to fill up.
I've seen 40% or more of the storage-drive taken up by this caching.
1/
I can tell you from experience of hosting many people's Fediverse server instances for a number of years now that —
Many Fediverse software (at least currently) do a poor job of cleaning-up their various caches
Caching other people's profiles, images, posts, etc
And, this often ends up filling up the storage drive
And as a result, this is a very common thing that causes down-time for people. Probably the most common