Round Robin Scheduling Not Power-Efficient
Via_Patrino writes "While having to distribute load between several servers, round robin, or any other technique that balances load equally, is the most common approach because of its simplicity. But a recent study shows that trying to accumulate load on some servers can improve energy efficiency because the other servers will be mostly unused during off-peak periods and then able to make better use of power saving methods. Specially, where load involves lots of concurrent power-consuming TCP connections, which was the case in the study, a new load-balancing algorithm resulted in an overall 30% power savings. Here's the paper (PDF)."
This problem shows up in many places.
technical writing / development
Operators of multiple steam boilers have been dealing with this problem for a century. The number of boilers fired up is adjusted with demand, with the need for some demand prediction because it takes time to get steam up. This was done manually for decades; now it's often automated.
The same thing applies to multiple HVAC compressors. Usually there's a long-term round-robin switch so that the order of compressor start is rotated on a daily or weekly basis to equalize wear.
More and more, IT is becoming like stationary engineering.
We've been sacrificing computing power for efficiency for years. New Server CPUs tout thier energy savings atleast as much, and quite often more than they tout their computational power. As electricity gets more expensive and data centers continue to grow this trend can only continue; it's simply too expensive to a warehouse full of server racks unless you focus on efficiency.
I'm waiting for the first company to put a data center a few hundred feet under water, where the water temp is low. You'd be surrounded by the worlds biggest heat sink. The environmentalists would have a hissy fit but that's never stopped industry before, and of course you could argue that you are saving electricty on cooling.
You aren't sacrificing speed as long as you have properly benchmarked your servers, and understand where the performance hockeystick starts.
Apply a connection limit slightly below the performance hockeystick in your load balancers / content switches and you will get maximum power utilization with minimum performance impact.
One other way I see customers getting maxim utilization out of their servers is by using dynamic resource schedule and vmware esx to move virtual servers around behind a load balancer. At this point your load balancer can be set at round robin (or optimally least connections) and you can use VMware to realize the cost savings of running at 90% utilization vs 30% utilization.
BigIP's can use round robin and use prioritizing, in other words one server receives the most connections over the others. So how is this new?
14 soccer moms are taking the team of 14 kids to a game. They have two options:
A. Spread the kids among all the cars, and drive all the cars (14 cars)
or
B. Fill up a car, and send off. Repeat until done. (6 cars)
What is more energy efficient?
Soccer moms have solved this without statistical analysis or engine torque curves.
don't cut it off www.mgmbill.org
Here is the solution. In the winter run your web farm in the North hemisphere. In the winter migrate to the South hemisphere. Run it in basements of large apartment complex. Charge for the heating. Heating oil is going up the roof.
- these are not the droids you are looking for -