> assuming the 49 euro cent/kWh from the top Where do you live? That looks very expensive to me
Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
131–140 of 230 posts
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#132This general concept is very similar to Apple’s Bonjour based “Sleep Proxy” service. Basically, if you have an Apple TV or something similar it will automatically wake up a sleeping device when someone requests its services. SSH or media sharing for example. While a device is sleeping the proxy will keep advertising its services via Bonjour. Low power always-on Apple devices are sleep proxies by default but you can t…
It just listened to the fixed routes, woke the server and proxied the page when finished (sometimes took 2 loads)
But basically is the same as in the arzicle except I didn‘t need to manually WOL anything and my server just went to sleep by itself
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#133Smartphones can be connected for days on the internal battery, using well under a watt, and they can be ready to respond instantly, and they have an app container system that makes everything just work. I really think we need to start making Android servers a thing, at least for self hosting, maybe for everything. Judging by how WearOS seems to be able to run on 35mA or less, I think there's a good case for just maki…
but Android is just based on Linux, so in theory you could tweak a regular Linux server on ARM hardware to get good energy efficiency. The downside of Android is its reliance on Java, which adds a lot of overhead compared to bare-metal languages (I strongly believe - but have no sources or figures to back this up - this is why Apple phones have been faster and more energy efficient, especially in the earlier days (th…
I'v always thought it is how iOS manages threads vs in a way Android cannot. But all that info is from more than decade ago, so things may have changed. Can anyone chime in to explain?
To this day iOS feels snappier, perhaps lower latency input/output or something. Am saying as someone who uses and prefers Android and currently using Samsung Galaxy S10 phone (flagship phone line)
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#134Earlier quoted context omitted.
not necessarily, depends on the embodied emissions in the replacement gear. It is also surprisingly hard to get any information on those. I tried seeing if there were estimates of the kg co2 in a modern CPU chip but I found nada
> I tried seeing if there were estimates of the kg co2 in a modern CPU chip but I found nada Because they are in watts, not kg of CO2.
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#135Earlier quoted context omitted.
Reverse proxy on the Pi? If a request comes in for the server and x minutes have elapsed since last activity/WoL, send a new WoL. I'm a little out of my wheelhouse though. Maybe that would only work for HTTP which will not cover Time Machine? Does Time Machine run on a schedule? Add a cron job (whatever the Mac equivalent is) to send a WoL ~1min beforehand?
Reverse proxy means that your pi now has to handle all the traffic for Plex and any other services. It could also make other things difficult like CIFS/whatever else you're hosting. Depending on what Pi you're using, it's networking is over USB, and so is quite performance constrained.
I guess you could just attach an external HDD to the Pi. Thats worked for me before.
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#136Earlier quoted context omitted.
Indeed, modern hardware is getting ridiculously efficient, and if you go the extra mile to disable hardware you don't use, as well as strip your configuration to run only the software you absolutely need, you can really drive it into the ground. The later hardware revisions (such as 1.5) of the Raspberry Pi 4B, even with 8GB of memory, can idle at ~1.33W on WiFi with everything unnecessary disabled -- 2GB versions ar…
> For those who go, "but I need real power" There's also the flip side, which is "well since I already have real power..." I.e., like many HNers, I own a powerful coding/gaming Linux desktop with plenty of HDD space, which gets regularly backed up to cold storage. It does however use a frankly obscene 90W when idling, due to the GPU, fans, and multiple hard drives and peripherals. Building a separate, power-efficient…
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#137I wrote something remarkably similar a few years ago, for similar reasons. I was pretty baffled that nothing similar already existed. Auto-wake with the RTC timer was what I really wanted. Link, in case you care: https://github.com/mrmekon/circadian I have a "NAS", which is really an enormous desktop tower crammed full of hard drives. It auto-wakes once per day, pulls backups from my various servers all over the plac…
Did not know about /sys/class/rtc/rtc0/wakealarm — thanks!
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#138Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#139€0.49 / kWh is an insanely high price for electricity. Here in the US in Cali, $0.32 / kWh is considered a steep price. I've heard the price in Oregon is $̶0̶.̶0̶2̶ ̶/̶ ̶k̶W̶h̶ $0.20 / kWh. What gives.. why can't electricity be delivered less expensively / more economically in Germany? Edit: Thanks for the corrections regarding Oregon, makes me feel a little better about the situations elsewhere. :)
The challenge is more that electricity supply is not consistent, which luckily is easily remedied by investing in solar/batteries. It's not yet common for consumers to feed back into the grid.
Re: Saving Energy: Home Server That Automatically Suspends to RAM and Wakes Up Again
#140I was using hdparm on my rpi home server to turn off the disk without unmounting it. It was just a cronjob to turn it off at night, and it would stay off until needed. The first request would then take over 5 seconds to turn it on again, and it would remain on.