How can I reduce the amount of storage used by my Lemmy instance?
I’ve had a Lemmy instance running on a VPS with 100 GB of storage for a few months and it has filled up. I’ve been searching for ways to reduce the amount of storage used but so far I am coming up empty. Can anyone point me in the right direction?
Firstly move pict-rs to object storage. My instance’s pict-rs uses 150GB alone. I pay less than $2/mo to put it on Cloudflare R2. Backblaze B2 might be even cheaper. Instructions: crates.io/crates/pict-rs#filesystem-to-object-sto…
If that doesn’t help enough and you’re comfortable with SQL, you can purge the unnecessary entries in received-activities.
Command: delete from received_activity where published & NOW() - INTERVAL ‘3 days’; (Lemmy has problems with ampersands so you’ll have to edit it)
Then do a vacuum full received_activity; to reclaim the space.
This deleted 98 million entries for me and reduced my database size from 49GB to 20GB a week ago when I started running out of space. No other effect as far as I can tell. Thanks @illecors
what is stored in received_activity ? anything important? I mean obviously it’s something the instance has received from other instances but is this then stored somewhere else (like comments then stored elsewhere for eg)
it’s in alpha currently, but you could still run it
I think you might have to use the :dev tag to get this update, a bit risky to stay on that tag though, maybe wait for the next docker image of an alpha release
I ran into the same problem and ended up switching to an S3 with Vultr. It’s been a while since I did it but here are the links that I used to figure it out. I’m deployed using Lemmy-Easy-Deploy.
So I wanted to try it and found that Synology offers 15 GB for free so I tried it and it was extreamly easy to do. Set up a bucket and then fill in the ENV variables in docker-compose restart and it works, impressive. I might really need to think getting a good deal and doing that for my other fediverse stuff like Mastodon, Peertube and Matrix too, I think it’s equaly easy there.
Sadly, no. My server has been a bit neglected but it’s been plugging along and working fine for the most part. I need to upgrade though. And I assume pictrs but to be honest I haven’t checked. I just noticed today it was running poorly and checked and the drive is full.
Instead of using the hard drive for pictrs, I suggest using it’s S3 capabilities and migrating to bucket based storage. You’ll save way more money and keep the expensive VPS hard drive just doing text and DB things. I think I spend maybe a dollar a month in S3 storage.
For anyone doing this, set up your spending and budget alerts and actions. It’s possible to accidentally fuck something up and end up with an aws bill that’ll suck, but this will give you some measure of protection from that in case you accidentally misconfigure something.
Add comment