get a platinum rated power supply, if you can afford it go for a titanium. The efficiency in the power supply is half of the efficiency of the rig
reduce the number of the modules to the minimum
get a platinum rated power supply ;)
get big passive coolers, you want to idle the fans
reduce the number of usb and connectors to the minimum. Their converters are not the most efficient. Try not to connect enything on them.
NO mechanical parts (including fans or water coolers)
set schedulers to conservative or power efficient. You don’t want to spike the power just because a task is 2ms longer than expected.
pick a power efficient CPU/gpu (I think we can discard this one based in your choices)
use the latest amd adaptative undervoltage technology to ensure to reduce the wattage of the cores
try to reduce to the bareminimum the number of background tasks /services running.
And that’s all. Sometimes there is a component of trial and error because sometimes the curve performance / power is not entirely linear and you don’t want to hit exponential-non-linear zone.
Good luck and if you can post you build with numbers and some lessons learnt would be great
Just to add my experience about PSU efficiency: for low power consumption (20-50W) you need PSU rated for minimum power your system needs. So if you are idling at 30W on 700W PSU your efficiency will be super bad because that PSU was made for higher loads and you are using <10%. No matter what PSU class you choose, efficiency will be better if your usage is at 40-70% of PSU max power. This is based on testing multiple desktop ATX PSUs for my small homelab
Leave Servarr as last thing to setup because it requires many services to work together and even small mistake in config will make it not work. Its not hard, but it will be easier after you learn how to setup jellyfin or audiobookshelf.
I have no experience with your hardware, but after you install docker and docker-compose get Portainer and get familiar with docker compose. Portainer is simple gui that lets you manage all containers.
So for example, you get docker-compose example for jellyfin, eddit PUID, GUID, path to your library folder, copy that in Portainer Stacks, hit deploy and BAM! Your jellyfin is available on localhost:8096
You might face many issues in the begining, but dont give up, its getting more and more easy over time. I still think Im a noob, but have no problems with my 40ish containers running on poor home server 😉. Dont forget this community is awesome and helpfull
Ceph, GlusterFS, and I suspect SeaweedFS (but I haven’t used it) expect high speed, low latency connections to their peers. So they won’t work well over the internet.
There’s some info floating around about using IPFS as the backend for Jellyfin, which in theory should allow you to share media between friends, but I haven’t tried it.
Do you have a NAS at home with enough storage? You could use wireguard to setup a vpn tunnel, then mount your NAS’s storage on your vps via nfs and using cachefilesd. If your upload speed is sufficient, this can work pretty well without too much waiting for a stream to start.
And also get into proxmox. You can pass through part of your GPU into a “desktop” environment and also have another VM(s) running in the background. That way you can use your computer as normal with a type 1 hypervisor in the background.
Also get a mobo with 2 NICs. The fewer pcie cards you have the lower power draw.
My NVMe idle at 7w and my HDDs idle at about 15w I think. 45w is just for storage.
Yes, it’s been on my roadmap for a while. I also created a pull request several months ago to enter the repo but it was never accepted (it’s also my fault because I didn’t follow the verification process properly).
Proprietary when flatpak exists, and it doesn’t properly address how apps should dynamically request access to things they need. Every time I’ve used either solution I’ve run into some permissions problem.
For desktop apps maybe. How do you run a flatpak from the cli? “flatpak run org.something.Command”. Awesome.
Both suffer from not making it obvious what directories your application can access and not providing a clear message when you try to access files it can’t. The user experience sucks.
It amazes me that all it takes is just changing user agent to Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) and it can bypass paywalls on many sites? I thought those sites would try harder (e.g. checking if the ip address is truly belong to google), but apparently not.
Same. I thought there would be more stuff happening in the background but when I saw it’s just hijacking the google bot headers to display the html i was a bit disappointed it’s so stupidly easy.
Checking ip ownership is a moving target more likely to result in outcomes these sites don’t want (accidentally blocking google bots and preventing results from appearing on google).
Checking useragent is cheap, easier, unlikely to break (for this purpose, anyway) and the percentage of folks who know how to bypass this check is relatively slim, with a pretty small financial impact.
Google literally has an official list of IP ranges for their crawlers, complete with an API that returns the current IP ranges that you can use to automate a check. Hardly a moving target, and even if it is, it doesn’t matter if you know exactly where the target is at all times.
It’s insane how many things they push as Snaps when they are entirely incompatible with the Snap model.
I think everyone first learns what Snaps are by googling “why doesn’t ____ work on Ubuntu?” For me, it was Filebot. Spent an hour or two trying to figure out how the hell to get it to actually, you know, access my files. (This was a few years ago, so maybe things are better now. Not sure. I don’t live that Snap life anymore, and I’m not going back.)
Yah, it’s been trash from the start. I tried it 2 years ago and the unpredictable weird shit it did was useless to try to troubleshoot. It was worse than trying to run Docker on Windows, if that can be believed.
Debian with the Docker convenience script is the way to run Docker.
selfhosted
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.