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
Might be a bit late on this, but ProxMox doesn't really handle assigning threads to the e/p cores. That's handled by the kernel and as long you're running kernel version 6.1 or greater you should be good on that front.
If you really need to, you can also pin specific VMs to specific cores. So that if you've got something that always needs the performance it can always run on the p-cores and things that aren't as demanding can always run on e-cores.
That said, especially if you're over provisioning, it's probably better to let the scheduler in the kernel handle thread assignments.