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:
- 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
Server CPUs are built for the workload (hosting / background services) rather than desktop applications for consumer PCs. That being said generally your going to be more limited in disk / ram than CPU unless if you have some specific needs.
In my setup, my server resources are averaging 10% cpu, 54% memory, and ~70% storage. I'm running 4 PCs, 8 cores each so 32 cores, currently on memory I got 2x64GB and 2x16GB so 160GB ram. Between CPU and RAM I am utilizing basically 3.2 cores worth of processing and 86GB of ram. Most of my ram is going to postgres databases for speed improvement and it takes off load from the CPU.
ok