Selfhosted

58148 readers

1131 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

Power efficiency (lemmy.zip)

submitted 2 days ago by jobbies@lemmy.zip to c/selfhosted@lemmy.world

47 comments fedilink hide all child comments

I'm wondering what folks do to optimise the power efficiency of their Linux servers. I've never really got to the bottom of what is the best way to do this and with the current energy crisis its a pertinent topic.

I'm talking about home servers, so the availability requirements are not the same as in a corporate environment. There might be vast chunks of time during the day or night when they sit idle, and home users are more tolerant of a lag when accessing resources if it means lower energy bills.

Specifically I've been thinking about:

allowing lower power states when idle
spinning-down hdd's when they're not in use
MAYBE letting machines sleep/hibernate
setting schedules of times where you know demand will be low/zero and efficiency can be managed aggressively
any other quick wins I've missed

It would be amazing if there was one tool or one guide that helps with all of that but thats never the case, is it 😅

Thoughts?

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

[–] notabot@piefed.social 3 points 2 days ago (1 children)

WoL works, but your server will take some time to come back online, but the router probably wont be able to buffer the traffic for that long, and a tcp connection would likely timeout before then anyway. You usually want to send the WoL magic packet, wait for the server to come back online, and only then start sending traffic.

[–] RIotingPacifist@lemmy.world 1 points 2 days ago* (last edited 2 days ago) (1 children)

What's the timeout on a TCP connect?

Could you not wake from suspend in that window? Maybe even a full hibernate?

[–] notabot@piefed.social 2 points 2 days ago

The TCP connection time out on linux defaults to a bit over two minutes, although individual client programs can use different values, and I'm assuming Windows is similar. Honestly, I was thinking about the time to boot a server, but if you're just suspending you'd almost certainly be ok, albiet with a slight power draw even when the machine is not in use. Hibernating might also be ok as long as your hardware gets through its POST quickly.