2026-09-06 10:47 UTC
Hmm, giving some consideration to switching over to #GoToSocial, and installing it bare metal on my VPS. At the moment this #Mastodon server runs via #Yunohost and the biggest pain in the ass is waiting weeks for them (Yunohost) to update the installers after a major Mastodon upgrade.
GTS appears to be a single binary, a database file and a YAML config file, running via one systemd service.
That's a lot less complex than Mastodon, with its multiple processes and connections.
Not to mention the resource usage.
After 10 months of operation, the database on this Masto instance fluctuates between 17Gb and 25Gb. Most of which is account data.
The same instance running under GTS as far as I can tell would be sitting at about 3gb at this point.
Memory and CPU usage would see similar reductions, which would be beneficial come renewal time and potential massive cost increases...
The main thing holding me back is the ability to use Quote Posts. I know it's coming in GTS, but there's no timescale AFAIK.
I know I originally had GTS installed prior to switching to Mastodon, but in hindsight I maybe should've stuck with GTS. I mean, Masto's been fine, but perhaps going lower resource would be better longer-term.
No rush to decide, as my vps is still 14 months from renewal, but definitely something to consider.
Replies (1)
-
@bryan@dusty.ninja 2026-09-07 08:20
@sar@social.elderlogs.net running in the provided docker container using only ENV variables is the way to go IMHO.