Selfhosted

54450 readers

862 users here now

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.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

ISO Homelab Power Saving Methods [SOLVED FOR NOW] (lemmy.world)

submitted 6 days ago* (last edited 6 days ago) by irmadlad@lemmy.world to c/selfhosted@lemmy.world

17 comments fedilink hide all child comments

In an effort to make the homelab more environmentally friendly, I have started to explore ways to conserve energy consumption. I always see a lot of considerations for choosing equipment that sips power, but other than avoiding enterprise power hogs and very old equipment, I don't see a lot of advice in how to tame the server(s) you may already have.

So far I've looked at:

TLP: Adjusts CPU frequency scaling, PCI‑e ASPM, SATA link power‑management
Powertop: Used to profile power consumption and has a tune feature sudo powertop --auto-tune
cpufrequtils: Used to manage the CPU governor directly
logind.conf: Can be used to put the whole server to sleep when idle

Since I am the only user of my network, and since a lot of times the server sits unused until I want to engage maybe listening to my audio collection via Navidrome, or perhaps I'm working on some automation in n8n, et al, there's no need to be at max power 24/7.

So besides just powering off and on the server, which would work but not be quite as elegant of a solution, are there other ways you have come across, read about, deployed on your own server?

ETA: Thanks for everyone's input. I realize that the ideal scenario is to have more energy effecient equipment. Sometimes tho, this is not a ready made solution due to many constraints. The exercise was to try to squeeze out every last little power saving option I could, without obviously replacing equipment.

Many thanks.

you are viewing a single comment's thread
view the rest of the comments

[–] ISolox@lemmy.world 4 points 6 days ago

This is pretty tricky. Sure you can tweak your CPU all day to try to get some lower power usage, but to get more drastic changes, it really starts at the hardware your using. I would suggest getting a N100 nas maybe? But it kinda defeats the saving money on power usage if you have to spend $150-$300 to do so.