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.
Resources:
- 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
Why do you need so much ram in your NAS?
ZFS. It can use up as much RAM as you care to give it for caching. So if you are slinging a lot of data back and forth, more RAM is better. Especially if you are using HDDs instead of SSDs.
And bumping up the RAM for caching makes a HUGE difference in performance on a RAM starved system. Going from 16 to 32 gigs almost doubled my read write performance for anything other than tiny files here and there. And overall I/O latency tanked.
Why do you need to cache data? To seed a lot of torrents?
It's a function of ZFS itself. Data that is to be written to the drives is first written to RAM, then transferred to the drives. One of the benefits of this is that if you are moving a file that is smaller than the available RAM, your transfer won't appear to be limited to the write speed of the drives.