I recently had to expand my instance’s storage size from 25 GB to 50 GB because it was out of space. How much storage do you all use for your instances? I’m a little surprised that it ran out of space as my instance isn’t heavily used.
Am I doing something wrong? I prune all the unused docker images, so it’s not that.
@dessalines@lemmy.ml how much space does lemmy.ml use?
Pretty much nothing, postgres volumes folder is ˜500MB, but that really doesn’t change much. Remember that text data really doesn’t take up much space: all of english wikipedia is about 20 GB.
Picture storage in pictrs is the main issue. The only thing I could suggest there, is to use either a remotely running pictrs, or to use sshfs to mount the pictrs volumes folder to a remote machine (non-VPS) that has a ton of storage.
You could also delete old pictures. I think mastodon does this.
I’m not familiar with pictrs and how it works, but software I wrote which contains thumbnails and full copies of every image on the fediverse along with fingerprints, full database metadata, etc, doesn’t take up even a tiny fraction of that space. So…
mastodon only does this for remote content!
TIL! What’s your mastodon acct username?
sorry I am not saying, I want to keep the identities separate.
Same deal here lol
good! It’s better to be safe than sorry ^^
deleted by creator
I really don’t want to add a photo editing suite to lemmy-ui. Picture and video processing is something that should be done as much as possible on the server.
I do
- remove pictrs temp files
/tmp/magick-* - recompress overly large image files
- truncate docker logs which frees up a lot of space
recompress overly large image files
When I was looking at some very old posts from feddit.de they had terrible jpg compression artifacts, is this the reason?
- remove pictrs temp files
Wow yeah that is pretty fast growth!
@wintermute@feddit.de how much space does our server use?
Right now 13GB
I just saw in the Lemmy matrix chat that you cleared up a lot of space by truncating logs. Where are those?
you could
truncate -s 0 /var/lib/docker/containers/*/*-json.log(which might break logs currently being written), configure logging viadocker-compose.yml, or even better/etc/docker/daemon.jsonThanks. I’ll have to look up how to configure daemon.json. I just truncated the logs for now. I wish I had known about that earlier! It cleared up about 15 GB of space.
deleted by creator
Wow, logs take up a ridiculous amount of space!
you could also free up space on pictrs
docker exec -it YOUR_PICTRS_CONTAINER /bin/sh -c "rm /tmp/magick-*"Hmm, tried that. It said no
magick-*files exist.hm, maybe this problem has been fixed
okay that’s not too bad.
