Is it worth it making a ZFS partition with compression for Postgres in order to save space? I assume since it's mostly text it should compress fairly well.
Or is there a better FS for compression?
@Moon
How big is it a CPU hit? My Masto VPS only really gets pinned when someone posts a bigger non x264 video and it starts transcoding
@lewdthewides
@Moon
Mastodon seems to be more efficient with DB usage than Pleroma, however since server has NVME all the queries are mostlikely CPU bound which means it could perform worse.
I might copy the DB to my PC, spin up VM to test it first.
I have a NVME drive and the same CPU architecture so it should show conclusive results.
@lewdthewides
@Moon
I assume it's better for CPU usage when serving AP activities because it doesn't have to create it, just queries the db and serves it?
@lewdthewides
So basically if you were doing this you'd be doing it to save space. I can't say what the performance implications are. I've ready typically that copy on write filesystems are bad for databases but there are multiple guides on hosting your postgres db on zfs. Either it's tolerable, or these people aren't having performance problems because they're not taxing the db. pleroma will tax the db. So, I just don't know.