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
I wouldn't do that if you have the hardware to keep things separated but it's because of what I run on my server. You need to take into consideration that besides CPU/GPU usage a server's heavy load will be on Network and Disks, so while the system looks like it's not doing much, it might be doing a lot of Io operations. The thing with that is that both your disks and your network have a limited capacity, so if you're trying to play a game you might get longer load screens and higher ping that you would with one machine for each.
That being said it vastly depends on what you're running on the server, but higher pings and lower fps are a given since now you'll have more processes running on the background, so for games that are CPU bottlenecked it will be a massive hit.