Hacker News new | past | comments | ask | show | jobs | submit login

It's also worth mentioning that, by his own admission, OP only managed to save less than 2 euro cents per day (60 / 3360).

Maybe he has different ideas, and that's perfectly fine, but personally I value reliability and uptime far more than 2 cents.

EDIT: I failed at math. See below comments. :V




About 41 euro cents per day->57€/140

3360 is the number of hours in 140 days.


You are, in fact, correct. I have no idea why I converted 140 days into hours...

Still, my point remains unchanged: I, at least, value reliability and uptime more than ~43 euro cents.


43 cents / day is >150 a year, that's not to be sniffed at.

Actually, at 150 / year you can rent a VPS (or two!) as well, always-on etc, which... kinda shows how skewed consumer price for electricity is.


your VPS will have a shared CPU with hundreds of other customers... So will probably be using far less power (for you) than your home server.

In Europe at least, most industrial users were paying more for electricity than residential users over the winter (gas shortage). Governments subsidized residential users more than most businesses.


And doing this is not going to largely affect the energy usage of the EU - at least, in comparison to, say, Dell putting Platinum rated PSUs in their workstations and AMD making good server chips that are twice as efficient at the same performance point as Intel's chips.


Or the energy usage of Germany’s chemicals industry…


Or the energy useage of 1 metal smelter.


Or the cost of running water pumps for public fountains


The romans had water fountains and no pumps.

Perhaps you underestimate gravity.


Italy is pretty mountain rich - central Europe though?!?


Did I mention the Romans. I was talking about modern fountains some of which have pumps


Ok, the implementation wasn’t very fantastic cost wise. However I still think this could be a big area of improvement. How can we reduce energy usage of servers?

There’s a lot of work with ARM lately, I’m curious if that could be used in server workloads like this.


The most effective way is to be able to dynamically distribute load across a large array of servers, turning some off at times of lower load. Anyone who runs a large datacenter probably already does this or something equivalent, either to save money or to service more customers with the same amount of hardware. It's more effective to optimize the hardware architecture, but it's worth noting that improvements in efficiency usually don't translate to reductions in power consumption. Instead, it causes induced demand and usage increases to fill available capacity.


> Anyone who runs a large datacenter probably already does this or something equivalent, either to save money or to service more customers with the same amount of hardware.

Possibly, but few cloud providers actually do live migration[0] since it's risky to pause a VM for typically less than 1 second, but up to 5 seconds.

0: https://cloud.google.com/compute/docs/instances/live-migrati...


Real world pause times for live migration are mostly imperceptibly small. Like, you might as well have a router glitch for the same whatever milliseconds.

To demonstrate Ceph RBD network block storage back in the day, I ran VNC sessions to two libvirt hosts and live migrated a full VM with a desktop and a bouncing ball animation in a window between the two hosts & VNC sessions. The only thing a human could perceive was that the desktop image in one VNC window goes black, and the animation continues in the other.


I was actually thinking about elastic AWS instances when I wrote that. IIRC they're meant to be spun up and then shut down as a service's demand varies.

VPS providers are already overprovisioned anyway, so they have less idle hardware to begin with.


Isn't that really expensive? Far more expensive than just keeping a cluster running 24x7? I think the much bigger cost here is shelf space and the hardware, and so the retail price isn't impact much by the cost of power.

For the record I like the concept and hope it becomes a lot cheaper over time.


And you can have most of it with a banal sleeping/waking up by the schedule. Regular Joe sleeps at night and works at day.

EDIT: btw, this solves "if Time Machine starts a backup" completely.


I have a backup box that wakes and does it's thing every night then shuts itself down when it's done.

I have a Plex box that turns on after work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: