Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Do you have a source or benchmarks for the last bullet point?
I am skeptical that optimizations like that wouldn't already be implemented by postgres.
Edit: Btrfs has the worst performance for databases according to this benchmark.
https://www.dimoulis.net/posts/benchmark-of-postgresql-with-ext4-xfs-btrfs-zfs/
Postgresql, or any database, don't compress its database files.
As the checks are done in the database files, at the disks, but cached in memory, when it does some expensive check or put any data into disk, if the data is compressed, then it will be faster.
I only have old data, but this could be of help, compression help disk reads and writes, even facebook uses btrfs for disk compression. Everyone should compress their databases in 2026, it makes it take less space and faster.
Edit: specifically, on the postgresql database, there isn't the default configuration without compression, but you can take some guesses from the other benchmarks, and these are old benchmarks, things changed since 2017, 9 years ago.
Edit 2: These are more noticeable on the data being capped by the ssd/hdd or sata connection, as it's a raspberry pi, it will surely be capped by the data transmission, sending and receiving less data will make the reads/writes faster.
Edit 3: This is another benchmark too, not postgresql, but on limited bandwidth to the disk