Power Consumption and the Future of Computing
mrdirkdiggler writes "ArsTechnica's Hannibal takes a look at how the power concerns that currently plague datacenters are shaping next-generation computing technologies at the levels of the microchip, the board-level interconnect, and the datacenter. In a nutshell, engineers are now willing to take on a lot more hardware overhead in their designs (thermal sensors, transistors that put components into sleep states, buffers and filters at the ends of links, etc.) in order to get maximum power efficiency. The article, which has lots of nice graphics to illustrate the main points, mostly focuses on the specific technologies that Intel has in the pipeline to address these issues."
anyone ever compared power usage (say, per flop) advances to the power usage (per mile) advances of our innovative combustion engine indutry?
My turnips listen for the soft cry of your love
With the availability of PC power supplies* in excess of 1000 watts, and the mine's-bigger-than-your's demographic, I wonder what bearing this has on power consumption also. Perhaps peripheral manufacturers need to concentrate on power usage also.
b mit=ENE&N=2010320058+1131428171
[*] - http://www.newegg.com/Product/ProductList.aspx?Su
boycott slashdot February 10th - 17th check out: altSlashdot.org
The problem is the massive rollout of servers and blades into datacenters that under utilized. The One Job One Box Syndrome. Most DC hardware is barely used but there it sits idling and sucking power. If we leaped into massive virtualization we'd be able to reduce the number of physical components and save power.
The thing with power usage is that nobody seems interested in attacking the 2 largest areas of power wastage. (except maybe google)
#1. DCAC conversion.
Your typical Datacenter has a UPS or batteries and inverters (Enterprise scale UPS). What this amounts it is AC power from your utility company converted to DC for storage in a battery and then converted back to AC to supply the Server's power supply, then converted back to DC to actually run the components of the computer.
Ever notice how hot a UPS gets during normal operation? That's power going to waste. The solution is to run our servers at a standardised DC voltage. 48 Volts sounds good since that is already defined for Telecom equipment (correct me if I'm wrong. I am not sure of the figure)
#2. Raised flour and underground AC. A good chunk of datacenter power is used to run the air conditioning. If we abandoned the notion of raised flours and replaced them with say insulated celling mounted ducts with vents faceing each rack.
While we are at it here is another simple power tip. Turn your rows of racks back to back. When they all face the same direction, hot air blows from the back of one machine to the frunt of another, forcing the AC to work overtime. In my design, I would have extraction fans betwean my back to back racks, pumping the hot air outside (or into the office during winter. For those of you who have winter.
--= Isn't it surprising how badly I spell ?
A couple of months ago, Luiz André Barroso of Google gave a talk at Stanford about this very topic. Unfortunately the talk wasn't recorded, but here's a summary: http://cs343-spr0607.stanford.edu/index.php/Writeu ps:Luiz_Andr%C3%A9_Barroso
I have been wondering this for a while now.
Why can I sit here and type this on a laptop that is faster than a top-of-the-line 1U rack from 1 year ago, and yet data centers are still loaded with power-sucking 3 year old machines by the thousands?
What you need in a data center is a) Performance, and b) Reliability. Performance is already covered - every year laptop speeds match the top speeds of the previous year's desktop machines. So you're at most a year behind the times. As for reliability - anyone who works with data centers knows that reliability does not come from reliable hardwaye - it comes from redundancy. If you had a data centre built from laptops in a blade-style configuration, where any one could be swapped out at any time, you would have awesome reliability at a tiny fraction of the power useage.
Throw in some external iSCSI or ATAOE storage vaults, and you're good to go.
The future of desktop computing is 24/7 thin clients/home servers using less than 10W and passive cooling without fans, because for a typical 300W desktop 24/7 system you probably would be paying $100/month, more than a thousand a year. This is enough for 90% of users, those who are not after the latest/greatest 3D horsing power, those whose necessities are supplied with an onboard graphics chip such as Intel X3100 or even less. You would be surprised with the amount of computing power such devices have nowadays.
l
They do not use hard disks, but flash memory/pendrives as storage for the operating system and homedir, and are passively cooled, so they do not use fans, which are noisy and spend more energy. Massive storage (TBs) can be added if necessary, each one using an extra ~15W. A small list with some of them:
1) Linutop: http://www.linutop.com/
It comes with xubuntu, 280euros.
~6W, AMD Geode LX700 433MHz, 256MB RAM, Audio, 100baseT, 4xUSB2.0
2) Zonbu Zonbox: http://linuxdevices.com/news/NS9073106297.html
It comes with Gentoo Linux, $250.
~15W, VIA C7 1.2GHz, 512MB RAM, Audio, 100baseT, 6xUSB2.0
3) Mini Linux PC: http://linuxdevices.com/news/NS6372429785.html
Not sure about which Linux flavor it comes with, but if it runs Linux, it runs Ubuntu, $99.
~5W, 200MHz x86-compatible, 128MB RAM, Audio, 100baseT, 3xUSB2.0
4) OLPC: http://www.laptop.org/laptop/hardware/specs.shtml
Not yet available, but specs are fine for a home server + external storage, ~$100.
~2W (!), AMD Geode LX-700@0.8W 433 Mhz, 256MB RAM, Audio, LinuxBIOS (!), wireless connection, 3xUSB2.0.
Many others: http://linuxdevices.com/articles/AT4923746399.htm
Batch, PBS, NQS, SGE, Torque, LVS. . .
Choose your poison.
Deleted
dcpower
Salut,
Jacques
I should point out that there are words that sound the same, but dynamically reconfigure their spellings to do different jobs as required.
There are 10 kinds of people in this world: those who understand binary, and nine other kinds of people.
It's actually very common to have one box get elected to do any number of things - serve files, whatever. If it goes down for some reason, another takes over that function. It's redundancy and failover for reliability.
The nearest thing we have nowadays to assembler is tools for compiler optimisation and execution profiling. I expect that Google uses the latest and greatest of these. The simple fact is that nowadays Java is not particularly inefficient, especially when the competition nowadays works in more or less the same way. On the other hand it is possible to build really quite large programs out of Java relatively easily, and expect them to work. Just as you can build an apparently very efficient car (e.g. Toyota Prius) but there is a huge upfront cost in additional development and manufacturing which may outweigh savings compared to conventional technology, so the additional development cost and time to market of developing programs to use less power may exceed the savings. On the other hand, reducing processor power per cycle is a manageable hit with the huge virtue that it then has a vast field of application, i.e. almost every program that runs uses less power without further development. This is therefore the most sensible approach.
Pining for the fjords
Of course, these are all small workgroup or very small Internet servers. It would be of no use for a server which would be at the max speed most of the time.
Anyway, I haven't had an opportunity to meter the difference yet to see how much power that really saves. Does someone know?
I've seen a number of posts about how smart it would be to use laptop components in servers. I disagree.
Most server farms are running at full speed 24 hours a day. They don't throttle back and would not spend much if any time at a low-power idle.
There are job scheduling programs where if servers aren't doing real-time stuff, they are backfilling with other jobs. Stuff gets queued up for literally weeks. It has been my experience that users demand more cycles -- not that the systems sit there idle just heating air. The systems run full speed as long as they are up. You can't idle down drives either - both for reliability (will it spin back up?), data latency, and just the fact that a data center is pretty much constantly riding a disk farm and if anything, you would want even more bandwidth than you already have.
Having them go to a low-power state when idle would really only benefit when we take the machines for software upgrades and such and we already try to minimize that time as much as possible. The bigger benefits will come from making everything as efficient as possible - i.e. power supplies, processors (and yes - even having those cut out parts that aren't being used when not used), cooling, etc.
Laptops like to idle between keystrokes and when data on drives isn't being accessed. Those stuations are really not seen in data centers.
Google isn't stupid; if that sort of improvement were available globally they'd be using it. My understanding of Google is that most of their work is I/O limited; assembly isn't going to help that much. Furthermore, the cost of reliably converting code to assembly would be immense and would divert labor from more profitable pursuits.
Contribute to civilization: ari.aynrand.org/donate
i beg to differ. Most servers are NOT running 100% 24/7. If they are, they haven't been engineered properly.
.05 load. There is no real reason to run them at 300W when they can easily run at 50W with the same visible performance to the end user.
Take a walk through a general use datacenter and you will find lots of 1U single use, non-clustered servers burning energy at full speed and running at
There ARE specific applications that would utilize the hardware 100%, but those are a small percentage of the servers in the real world.
Where this would become important is hundreds and thousands of servers that could run at ~50W instead of 300W. The energy savings alone to the facility would be something that would make a CFO weep.
Why read the article when I can just make up a snap judgement?
Most server farms are running at full speed 24 hours a day.
Afraid not. Data center utilization is typically 20%, and often a lot less. A very lot less.
C//
Maybe at your data center. Maybe I shouldn't have said most data centers. And we aren't running underdesigned systems. We are running the fastest and biggest we can get. For modelling and simulation work, the loads are high and pretty continuous.
Here's a video.
every year laptop speeds match the top speeds of the previous year's desktop machines
Comparing laptops and desktops is irrelevant when talking about data centers since they use servers. The fastest low-end server from one year ago was a 4-core 3.0 GHz Woodcrest system, but the fastest laptop today is only 2-core at 2.4 GHz. Not to mention that last year's low-end server can hold 16-32 GB of ECC RAM, and today's laptops only hold 4 GB non-ECC RAM.
RLX and HP tried building servers from laptop components back in 2001-2002, and there weren't enough customers to keep those products going.
EnergyStar standards for power supplies are that no more than 20% of the AC power be converted to heat going through the transformer - which means that on most systems more has been turned to heat in the server room before it does anything. Just moving *that* heat conversion out of the server room where it does not need to be cooled away is a big win. Remember, it takes, in a well designed system, 1.7 times the energy to cool a space as it took energy to heat it. Opponents of DC in the server room usually miss this aspect.
Centralizing of the AC/DC conversion allows for the possibility of selecting much more efficient transformers. But we can quibble over that. In any case, isolating and concentrating just *that* portion of the heat enables new approaches. I have seen Absorption Chillers running off the transformer heat being used to boost data center cooling. I have seen domestic hot water heating. I have been in serious conversations on Stirling Engines running of the transformer heat to charge the batteries.
The highest performance versions of this are not actually about saving energy - they are about running the computer flat out. How hard can I run the machine? If the transformer and power distribution are running well, can I use my redundant power to double my machine power rather than providing redundancy? Can I do early detection of potential power failures and then back off...
For modelling and simulation work, the loads are high and pretty continuous.
Sure, but this is a minority. I think it's more likely that most servers in the world are running stuff like databases, email, Web, business applications, etc. When there's no work to be done, they just sit idle.
Power usage is horrid. A 600MHz ARM Xscale has better performance per clock than a 600MHz x86 and eats half a watt of power; while 1.2GHz Core Solos eat at least 10 watts and most other processors around 2-3GHz eat 60-120 watts, some even 180 watts! That's between 5 and 36 times more power per clock cycle; and most of the newer chips are RISC processors on a proprietary instruction set with a real-time translator from x86 to internal RISC. It takes HOW MUCH power?
_ Usage_Machines
I've actually brought this up on Dell's IdeaStorm, if anyone cares (link below). Seriously, look at the OLPC, look at ARM processors, look at how modern computers work, we don't need to be burning that much power. I can't comment directly on these 100 watt video cards as of yet but does a GPU and some RAM need that much power itself? Data centers put stress on the grid, our home PCs stress the grid and cost us money, and laptops and UPS-backed machines have battery life when wall power goes away. We NEED lower power usage.
http://ideastorm.com/article/show/68285/Low_Power
Support my political activism on Patreon.
You're right. You should not have said "most".
Modsim is a unusual use case. That use case has its own concerns.
20% is really on the high end for utilization in virtually every data center.
The syndrome that is most alive today is the "one service, one box" issue. That's why all the drive for consolidation, coming from the virtualization vendors.
C//
I'm going through the exercise this month of replacing a whole slew of my always-on Internet servers at home (HTTP, SMTP, DNS, NTP) on machines going back long enough to still be running SunOS 4.1.3_U1 in one case, with a single Linux laptop. Current power consumption is ~700W. Target power consumption for the new system So, it is doable and worth doing financially, and I don't have to pay the 3x extra cost right now to remove the heat with aircon (if I did, I could pay for the solar panels too power it even in midwinter too).
See http://www.earth.org.uk/low-power-laptop.html
Rgds
Damon
http://m.earth.org.uk/
I'm not, in fact, absolutely clear what you mean in your post. There is a difference between implementing redundancy and failover as a policy, using dedicated hardware, and the idea of having servers get together and somehow vote on which is to fulfil a management function, which the article suggests.
Could you clarify what you are saying?
Pining for the fjords
Thank you for confirming my suspicions. I wonder what I've done to upset you?
Pining for the fjords
Ideally (not stuck with hardware designed for an office environment) you do this:
Air should flow from cold aisles to hot aisles by a simple pressure difference. Those little CPU fans generate heat and lots of noise. It's better to rely on airflow supplied by the building. This of course means that the cases have ductwork and aerodynamic heat sinks as required. I've seen it for a single rack; it's really nice to eliminate the individual CPU fans. Reliability goes up (no CPU fan failures) and noise goes down.
There is some advantage to grabbing outside air, using it once, and then venting it up a chiminey. Modern computers don't need to be all that cold; for the drives it is even bad to be really cold. (see Google results) Cooling the air is expensive. Of course, some places have extreme variation in outside air temperature that must be considered.
For the UPS, water towers sound nice, but I haven't done the math. It's like having your own hydropower station.
Google isn't stupid, which is why they aren't running the world's most power-efficient data centers. Quite the contrary, actually. My educated guess is that Lexis-Nexis has a per-search energy use profile vastly lower than Google's. (No, I don't work for Lexis-Nexis nor have any inside information. I've just reviewed public information about them.)
Google has tons of money, so they don't particularly care about energy use right now. But that lack of caring will come to and end one way or another.
I think servers are probably much more important than desktops in terms of power savings, just because they are on far more of the time....
Using a Killawatt, I was able to measure usage of some tasks with the CPU forced to 350MHz in comparison with allowing it to manage its own power. While it was by no means a well designed experiment, it seemed fairly obvious that the system always used less power when allowed to manage its own power usage.
Am I the only one who thinks Aero graphics is an environmental disaster...?
I don't know who needs 1000W but it's easy to make SLI gaming rigs go over 500W.
Stick a couple of the "twin power connector" cards in a box with a big CPU, overclock the hell out of it...that's four or five hundred watts right there.
No sig today...