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
It was an 8 core. But the current server is a 32-core / 64 thread cpu.
For only 17k Users? Seems like a lot of CPU Usage. Damn.
it's most likely coming from postgres, db server tends to be the main resource hog.
That image was from when we had 8 cores. Now it's under 10% usage :-) So we have some spare.
It seems a high usage to me as well... what's the load? (from the uptime command) I'm puzzled as the disk and network are basically idle (very low usage) but the CPU is basically saturated...
Beside this THANK YOU FOR YOUR GREAT WORK!