Cooling Challenges an Issue In Rackspace Outage
miller60 writes "If your data center's cooling system fails, how long do you have before your servers overheat? The shrinking window for recovery from a grid power outage appears to have been an issue in Monday night's downtime for some customers of Rackspace, which has historically been among the most reliable hosting providers. The company's Dallas data center lost power when a traffic accident damaged a nearby power transformer. There were difficulties getting the chillers fully back online (it's not clear if this was equipment issues or subsequent power bumps) and temperatures rose in the data center, forcing Rackspace to take customer servers offline to protect the equipment. A recent study found that a data center running at 5 kilowatts per server cabinet may experience a thermal shutdown in as little as three minutes during a power outage. The short recovery window from cooling outages has been a hot topic in discussions of data center energy efficiency. One strategy being actively debated is raising the temperature set point in the data center, which trims power bills but may create a less forgiving environment in a cooling outage."
Other publications have noted it was number 3, too.
DT
Is this thing on? Hello?
If you want 100% uptime, it's important to have back up power for the cooling as well as the server systems themselves.
Is this really news?
Well, back to rejecting software patent applications.
Actually this brings up an interesting point of discussion for me at least. Our office is doing a remodel and I'm specifying a small server room (finally!) and the contractors are asking what AC unit(s) we need. Is there a general rule for figuring out how many BTUs of cooling you need for a given wattage of power supplies?
I'm out of my mind right now, but feel free to leave a message.....
http://www.doc.ic.ac.uk/~matti/ise2grp/energystorage_report/node5.html
Man, I wish I was making that up.
Liquid nitrogen is the cooling answer, for sure. Then you're not dependent upon power of any kind at all. The nitrogen dissipates as it warms, just like how a pool stays cool on a hot day by 'sweating' through evaportation, and you just top up the tanks when you run low. It's cheap and it's simple. That's why critical cold storage applications like those in the biomedical industry don't use 'chillers' or refrigerators or anything like that. If you really want to put something on ice and keep it cold, you use liquid nitrogen.
A-Bomb
I've never understood why data centre designers haven't used a different cooling strategy to re-circulated cooled air. After all, for much of the temperate latitudes for much of the year the external ambient temperature is at or below that needed for the data centre so why not use conditioned external air to cool the equipment and then exhaust it (possibly with a heat exchanger to recover the heat for other uses such as geothermal storage and use in winter)? (Oh, and have the air-flow fans on the UPS.)
The advantage of this is that even in the worst case scenario where the chillers fail totally during mid-summer there is no run-away, closed loop, self re-enforcing heat cycle, the data centre temperature will rise but it would do so more slowly and the maximum equilibrium temperature will be far lower (and dependant upon the external ambient temperature).
In fact, as part of the design for the cluster room in our new building I've specified such a system, though due to the maximum size of the ducting space available we can only use this for half the heat load.
Agrajag: "Oh no, not again!"
After reading the articles linked from previous posts, it looks like the third outage was related to their cooling units not coming back online from the power outage linked to the Semi vs. Transformer battle. I know the units in our data center aren't hooked up to the UPS, but instead are wired directly to the generator in case of outage. I belive this is due to the massive number of additional cells that would be needed to keep up with the wattage requirements. The theory is that if the power goes out, you can live without cooling for the couple minutes while the generator pumps out the first giant plumes of black diesel and revs up to max capacity. We had a similar unplanned test when the local grid had a brownout. Luckily, our units functioned as designed. I wonder if their issues before did more damage to the units than they would have expected...
They should ban that stuff. (dhmo.org)
Give a man a fish and you have fed him for today. Teach a man to fish, and he'll say "WHERE'S MY FISH, YOU IDIOT?"
Ah, the dangers of context-sensitive advertising.
Ad on the main page when this article was at the top of the list.
Does "50% off setup" mean you'll only be set up halfway before they run out of A/C?
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
The first occasion was over a weekend (no-one present) in a server room full of VAX's. On the monday when it was discovered, we just opened a window and everything carried on as usual.
The next time was when an ECL model Amdahl was replaced by a CMOS IBM. No-one downgraded the cooling and it froze up - solid. This time the who shebang was down for a day while the heat-exchangers thawed out. It was quite interesting watching the temperature monitors, it took a couple of hours until the temperature rose above the "danger" threshold.
So the answer is either, until you arrive at work (2 days or more), or sometimes a bit more heat is a good thing.
politicians are like babies' nappies: they should both be changed regularly and for the same reasons
A few weeks ago the A/C dropped out in one of our computer rooms. I like the resulting graph: http://leebert.org/tmp/SCADA_S100_10-3-07.JPG
For those of you who either didn't take Physics, or slept through it, Watts and BTU's/hr are both measurements of POWER. Add up all the (input) wattages, and use something like http://www.onlineconversion.com/power.htm/ to convert. This site also has a conversion to 'tons of refrigeration' on that same page.
Also note - Don't EVER user the rated wattage of a power supply because that's what it SUPPLIES, not uses. Instead use the current draw multiplied by the voltage (US - 110 for single phase, 208 for dual phase in must commercial blgs, 220 only in homes or where you know thats the case). This is the 'VA' [Volt-Amps] unit. Use this number for 'watts' in the conversion to refrigeration needs.
Just FYI - a watt is defined as 'the power developed in a circuit by a current of one ampere flowing through a potential difference of one volt." see http://www.siliconvalleypower.com/info/?doc=glossary/, i.e. 1W = 1VA. The dirty little secret about power calculations is that there is another factor thrown in, typically about 0.65, called the 'power factor' that UPS and power supply manufacturers use to lower the overall wattage. That's why you always use VA (rather than the reported wattage) because in a pinch you can always measure both voltage and amperage(under load).
Basically do this - take all the amperage draws for all the devices in your rack/room/data center, multiply them by the applied voltage for that device (110 or 208) and add all the products together. Then convert that number to tons of refrigeration. This is your minimum required cooling for a lights out room. If you have people in the room, count 1100 BTU's/hr for each person and add that to the requirements (after conversion to whatever unit you're working with). Some HVAC contractors want specifications in BTU's/hr and other want it in tons. Don't forget lighting either if its not a 'lights out' operation. A 40W florescent bulb means its going to dissipate 40W (as in heat). You can use these numbers directly as they are a measure of the actual heat thrown, not of the power used to light the bulb.
Make sense?
Dennis Dumont
What happens when the primary, secondary, and tertiary air conditioners all shut down.
http://worsethanfailure.com/Articles/Im-Sure-You-Can-Deal.aspx
steveha
lf(1): it's like ls(1) but sorts filenames by extension, tersely
In a previous /. article (Ancient fridge)we learned that a sterling engine can run off excess heat, so why not power the cooling system with a sterling engine?
The hot air from the cabinates could be pumped by the Stirling engine to the sterling engine, the work done will lower the air temperature which can then be pumped back to the rack.
Now I realize that a Stirling engine might not be able to extract enough energy to cool a rack in a on-going way, during normal operation it could run in a supplementary capacity with conventional air conditioning but in a power outage it could well buy the extra time needed to either get the chillers running or shut down the servers.
In the not too distant future, next Sunday A.D.
One thing to consider is if the heat measured outside a box is high, the heat on the surface of the processor is much higher. Even with little fans or heatsinks on them, it doesn't do much, remember, fans and heatsinks don't change temperature they just displace heat - and the heat is attempting to be displaced in an environment of a lot of other boxes trying to displace heat.
In our current data center, run by a respected name, I have measured external temperatures in excess of 100 degrees Fahrenheit on some machines. Machines that run 24/7/365. We have small non-production rooms which have cheap fans that fill up with condensation, and a building staff which is supposed to empty the water when it fills up, but often doesn't.
Sometimes it gets kind of insane - I worked for a Fortune 100 financial company that had tons of money, and had a data center with Sun Enterprise 4000 series servers all over the place - yet the server room was above room temperature, and even more so in certain areas. We had disk and processor/memory board failures all the time, but they never really cared about the room temperature - they spent more time making sure the insides of the fibre optic cables were clean.
I have always brought up my concerns, but management has never really taken them seriously, and then I become overloaded with other work and forget about it as well. The ideal temperature for servers is a few degress above 0 Celsius, or even below 0 depending on the equipment. Meanwhile, if you find a server room where the temperature is below 20 degrees Celsius, you're lucky. It's just one of those things where it is cheaper and easier for them to just waste my time than to fix the problem.
Most large refrigeration compressors have "short-cycling protection". The compressor motor is overloaded during startup, and needs time to cool. So there's a timer that limits the time between two compressor starts. 4 minutes is a typical delay for a large unit. If you don't have this delay, compressor motors burn out.
Some fancy short-cycling protection timers have backup power, so the the "start to start" time is measured even through power failures. But that's rare. Here's a typical short-cycling timer. For the ones that don't, like that one, a power failure restarts the timer, so you have to wait out the timer after a power glitch.
The timers with backup power, or even the old style ones with a motor and cam-operated switch, allow a quick restart after a power failure if the compressor was already running. Once. If there's a second power failure, the compressor has to wait out the time delay.
So it's important to ensure that a data center's chillers have time delay units that measure true start-to-start time, or you take a cooling outage of several minutes on any short power drop. And, after a power failure and transfer to emergency generators, don't go back to commercial power until enough time has elapsed for the short-cycling protection timers to time out. This last appears to be where Rackspace failed.
Dealing with sequential power failures is tough. That's what took down that big data center in SF a few months ago.
The solution (no pun intended) is to use something other than water for coolant, such as a fluorocarbon liquid (Not to be confused wth ozone depleting chlorofluorocarbons...)
LFCs are electrically and chemically inert, allowing for direct submersion cooling. If that is undesirable, a normal "water block" heat sink can be used and leaks are only a mess issue, not a functional one.
"best" would be, IMHO, a heat pipe design inside the server module that brings heat to a contact surface on the back, which then thermally connects to a cooling backplate of some kind. This eliminates any liquid inside the modules themselves and mitigates the leak risk completely.
=Smidge=
You could do it, it's just probably more expensive than forced-air cooling.
What you probably would want to do is have a closed system that's actually inside the computer. Fill it with some sort of nonconductive/noncorrosive coolant that won't destroy the machine if it leaks (e.g. 3M Fluorinert), then have a cooling block on the back, away from the electronics, where you plug in the chilled water lines. If you don't daisy-chain, and instead end-run the water intake/exhaust lines from every machine to a central pump, and more importantly than that, you have it driven by suction on the return side rather than positive pressure on the supply side, you could easily attach and detach machines without leaks. (Since in a datacenter a leak is probably more disastrous than a LoC to one server, suction is preferable to positive pressure.)
You'd disconnect the supply from a machine using a quick-release valve; then wait a second for the suction on the return side to pull the water out of the machine's cooling block and start sucking air. Then you'd disconnect the return side. This obviously means that you'd need a way of separating the air out of the return side before it hits the pump, but that's not exactly a unique engineering problem.
It's all doable, but the problems are the expense and the standardization. There's a major chicken-and-egg problem with equipment: you don't want to build a datacenter that can't use commodity equipment, but hardware manufacturers don't want to build gear that can't go into a standard air-cooled rack. So even though datacenters may be the biggest purchasers of racked servers (I'm not sure of that but I suspect they are, at least of some types), and datacenters might be better served by some sort of cooling besides forced-air, everybody gets the lowest common denominator.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
It seems crazy that the data centres seem to run in hot states. Surely Alaska would be better? C'mon Alaska, get the tax-breaks right.
Engineering is the art of compromise.
I fail to see where this could be news to anyone who works with data centers. If you want your datacenter to operate during a power outage, you need a Generator with enough capacity for your servers/network and your cooling. If a fancy hosting site with SLA's making up-time guarantees doesn't understand this, I think thier customers should start looking elsewhere.
Keep passing the open windows...
The real solution here is not really a multihour ups for cooling and power, it would be a emergency generator. Have the generator auto kick on after 5 minutes and have 10 minutes of UPS time on the equipment. Generally I have found there is no need to ups the cooling unit.
While many here are discussing UPSes, chillers, set-points, etc the most serious flaw is being glossed over ... the lack of redundency outside the data center, such as multiple, diverse power lines coming in...
From the articles, it appears that Rackspace datacenter doesn't have multiple power lines coming in and/or many come in via one feed point.
How else is it that a car crash quite some distance from the datacenter can cause such disruption. Does anyone even plan for such events - I get the feeling most planners don't, since I've seen first-hand many power failures occur in places where one would expect more redundency from dumb things like a vehicle hitting a utility pole, etc.
Ron
We've summoned a small demon to let in cool air particles and shunt out hot ones. Sure the weekly sacrifice gets to be a pain after a while, but there's always a pool of willing interns right?
Ask not what you can do for your country. Ask what your country did to you
Every single watt consumed by a computer is turned into heat, and generally released out the back of the case. Computers behave the same as the coil of nichrome wire as is used in a laundromat clothes dryer. (I guess a few milliwatts gets out of your cold room via ethernet cables and photons on fiber)
5 kilowatts is a heck of a lot to have on a single rack - assuming you're actually utilizing that. I recently interviewed a half dozen data centers to plan a 20-odd server deployment, and we ended up using 2 cabinets in order to ensure our heat dissipation was sufficient. Since data centers are usually supplying 20 amp, 110 or 120v power, you get 2200-2400 watts available per drop; although it's considered a bad idea to draw more than 15 amps per circuit. We have redundant power supplies in everything, so we keep ourselves at 37.5% of capacity on the drops, and each device is fed from a 20amp drop coming from a distinct data center pdu. That way even if one if the data center pdus implodes, we're still up and at 75%- capacity.
Almost no data center we spoke to would commit to cooling more than 4800 watts of power at an absolute maximum per rack, and those were facilities with hot/cool row setups to maximize airflow. But that meant they didn't want to drop more than 2x20amp power drops, plus 2x20 for backup, if you agreed to maintain 50% utilization across all 4 drops. But since you'd really want to maintain 75%- even in the case of failure, you'd only be using 3600watts. (In the facility we ended up in, we have a total of 6 20 amp drops, and we only actually utilize ~4700 watts.
Ultimately, though, the important thing is that cooling systems should be on generator/battery backup power. Otherwise, as this notes, your battery backup won't be useful.
The one, seemingly obvious, question I have is, why aren't the cooling needs on generator/ups backup?
I have toured data-centers where even the cooling was on battery backup. The idea is that the battery banks hold everything as it is until the generators come fully online (usually within 30 seconds). The batteries/UPS transformers were able to hold the entire system for approx 30 minutes on battery alone irrespective of generator status. This also reduced the issues from quick brown-outs...no need to fire up the generator for a quick 2 second outage.
Why aren't data-centers like this built to be completely self-sufficient or autonomous?
Sig Return: 204 No Content
- Due to facilities issues (we are a State agency in a County controlled facility), our "data center" is a 6'x11' closet, so 66' sq.
- The sum of our equipment wattage in the "data center" is min=6510W max=16833W. We estimate the average running wattage to be around 11000W.
- Assuming 1W/h=3.414 BTU/h, our "data center" generates 22225 BTU/h, 37554 BTU/h, 57468 BTU/h, min, avg, max respectively.
- Due to the same facilities issues in #1, we keep the "data center" at 71 degrees F, and cannot keep it any cooler.
- Due to the same facilities issues in #1, we have lots of cooling outages, and therefore much experience that qualifies me to accurately answer the question.
If cooling goes out in our "data center," the servers overheat in 15-20 minutes (when the closet reaches about 115-120 degrees F). To increase this time to about 45 minutes, we have installed a portable cooler that kicks in when the main HVAC system fails.Back when I worked for the Secretary of State's office it was decided that we should move the Central Voter Registration System to a new location, along with all the other mail, web, and database servers.
I was responsible for infrastructure planning. We ended up using an APC Symmetra backed up by a 125kW natural gas fired generator. Transfer to generator took approximately ten seconds by the Symmetra could keep the whole thing running for 45 minutes, allowing us graceful shutdown, etc. if the generator didn't spool up. We even extended power to the MDF so that Cox could plug their UPS into the generator line and be powered up while everything else was down.
The cooling was accomplished by redundant systems. There were duplicate two-ton air conditioning units in the room. If one failed the other could pick up the slack but in normal mode they both ran.
This represented a big improvement over what we'd had before. The servers had been housed in an minimally air conditioned closet in the sub-basement of the State House.
The fly in the ointment so to speak was that we depended on another state agency for DNS service. One day there was a massive power outage that affected a good chunk of Providence,RI. The Sec State's office systems were up and running except nobody could get to them, and they couldn't get out.
And it's still that way today.
They sort of make what you are describing, many datacenters have glycol cooling and companies like APC make spot cooling solutions which allow you to bring the glycol loop directly to cabinets with unusually high power densities such as a rack full of fully populated blade enclosures. Now they are generally used to cool incoming air for normal systems because the laws of mass production means it is MUCH cheaper to buy a new cooling loop for the rack then it is to buy a rack full of specialized servers.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
Disclaimer: I work with SGI, so I can shed some light on their customer's perspective (NASA, gov't, research labs, etc.) and solution to this problem.
The increasing density of servers is exacerbating the problem of power and cooling in every data center. This week is the SuperComputing trade show where the the new top 500 supercomputers edition was released with "Big Turnover Among the Top 10 Systems," where you can see the first examples to address these issues.
SGI's new ICE blade system was launched a few months ago, it was designed to address the power consumption, real estate density, and cooling issues everyone will probably experience on their next server cycle. ICE has shipped and one installation is now #3 on the Top 500. It's a welcome sign that SGI is back from bankruptcy. I'm sorry if this seems like an advert, so I'm not going to link to SGI -- you can go find out more easily if you want.
My opinions are my own, but you may share them!
Go aircraft hardware, and be prepared to pay the price.
Stainless hard lines with short braided Teflon-lined hoses having quick disconnects (HAVE QD PLUGS/CAPS IN CASE THE QD CHECK VALVE LEAKS) could connect the cooling manifold to the servers. I'd use ozone-friendly refrigerant instead of liquid so leaks don't damage hardware. System pressure would be easy to maintain. Have a recovery suction line to each server so it could be emptied after being isolated.
Chilled compressed air would be another, simpler option. The condensation wouldn't bother aircraft hardware, and a large air tank would compensate for pressure variations.
A reason that 18-wheelers use air brakes instead of hydraulic ("liquid") brakes is that it facilitate quick disconnection and tolerates some leakage.
"This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
When i worked at (and help build) a datacenter back in 2000, they planned for just about everything. Then they played the whatif game for a few more scenarios, and came up with the fact that they needed to double the main capacity, and add a second layer. By that i mean that if the main transfer switch on the genset failed, there was a second one that'd kick in. If one or 2 (or all 3) of the A/C units failed for some reason, there was #4 and #5 which could carry the load with acceptable tolerances.
:)
We also had the genset in parallel to the UPS. So when the UPS got down to around 60%, the genset would kick in, and power them back up to 85% and shut down again. There was also 2 more gensets on site for just A/C and other essential systems. (We also learned the hard way how A/C compressors really dislike genset power, and had to get a very expensive line smoother from the power company to make the bigger ones play nice.)
Someone did the math on this system once. The datacenter could sustain itself without outside power for 51 days(!!) running at 70% capacity.
Not to mention, we ran the datacenter once a month for 6 hours on backup systems just to test. Then again, my boss at the time was the type of guy who would pull a card out of a router to see if said router (at that point in time, a Cisco 7513) was hot swap... Live router, had our SONET stuff running through it... Luckily it is a hot-swap router.
As computer get warmer there power consumption goes up.
http://www.silentcomputing.com/tech/market2.gif
Using Intel mother boards we found for each 10 Deg C temperature increase there was a 2% power increase.
I spent three years trying to get a company off the ground after I solved how to fix the heat problem.
I realized, they don't want to fix it, unless it's going to make them money.
I am always doing that which I can not do, in order that I may learn how to do it. - Pablo Picasso
Because:
a) It's turned off, as they want performance.
b) It doesn't apply to the other big heat-maker, the drives.
It's also a lot easier to cool and recirculate air, than to properly clean, (de)humidify and cool external air on the fly.
50% is outlandish. The number is probably 15-40%. But most importantly, you can't eliminate that loss by switching to DC. DC power supplies aren't any more efficient than AC PSUs. In fact, the two are largely identical.
And you simply can't run computers on a single voltage, or even a small number of voltages. Your CPU and other chipsets need anywhere from 0-3 volts these days. Motors, in hard drives, case fans, etc. are more efficient with the use of higher voltages. Different buses and ports require a range of different voltages. etc.
And even if you could standardize on a single voltage, you'd still need a power supply, because computers won't handle the voltage spikes and surges of a shared line, they need ultra-clean DC, so expect to pay ungodly amounts of money for ultra-massive banks of capacitors and voltage regulators, all with really no gain in efficiency.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Last night while spinning the channels on tv I saw a discovery channel/PBS show regarding a library in AZ using ice as a way to timeshift their power demands away from peak power load times. This system used a grid of refrigeration coils imersed in a tank of water, at night when power demands were lower, the A/C compressors would circulate refrigerant through the water tanks, freezing the water into ice, in the day they would dump the heat into the ice letting it melt. It seems a similar strategy would work for data centers for short term banking of lower powered cooling needs.
Ike
And stop running the SETI client, install the power scaling software of choice for your architecture, and stop wasting so damn much electricity to keep your precious snowflake busy 24/7.
I have a server in the DFW1 Datacenter that was knocked out during the first two outages but survived the third. I was down for about two and a half hours during the first outage and fifteen minutes during the second. My Rackers answered every question I had about it with honesty and humility. They admitted that this was their problem and kept me informed as to what was going on.
I'm wondering how many people posting on this thread are actual Rackspace customers. I can't say that I have ever once experienced anything less than top quality service from them. They are friendly, knowledgeable, hard working, and I respect them very much, and that's coming from a sysadmin/one man IT department.
Here's a company that is taking responsibility for its actions right off the bat, apologizing for their shortcomings, and honestly trying to make things right for those who have been affected. Think about this in contrast to the corporate scandals and craptacular customer service that has been plaguing the US lately.
That is to stop the CPU chip from permanently destroying itself by overheating (which it would do within seconds if the heat sink was removed, it could last a few minutes without a fan).
It will not affect the heat production of the rest of the system (PSU, motherboard chipsets, drives, etc.)
Furthermore, the performance drop when CPUs do this is so horrific you would do better to pull the plug on the machine, that way there a much more significant heat production drop.
Turning off a section of your machines is better than having them all/more of them effectively hung, and still producing heat...
There is no psychiatrist in the world like a puppy licking your face - Ben Williams
Why not use the power of the expanding nitrogen gas to provide power as well - and yet another use is to put out fires as well.
There's more than servers to consider. DASD doesn't like to get hot - at all. The motors used in the HDA's are not variable speed so they can't be slowed down, they are either on or off. Running DASD hot for any prolonged period of time is a good way to become familiar with the term " . . . may produce unpredictable results" (and none of them are good).
"The bigger the lie, the more they believe." - Det. Bunk
Interesting. Of course now we have the benefit of having cut out the middleman - by positioning the data center near the highway the truck doesn't have to bother hitting the transformer it can just ram directly into the data center. :)
"The bigger the lie, the more they believe." - Det. Bunk
I had an ISP that hosted my MySql-based app. The AC broke in their server room and the hard-drives got fried. They restored from the most recent backup, but it appeared they loaded from MySql dumps.
For some reason, auto-incrimenting columns in MySql re-assigned the numbers based on the order in the dump, bypassing gaps created by deleted records. Cross-references via the ID number were all screwed up. It was a pasta nightmare. I'm not sure how to prevent this in the future, other than manually program my own number assignments or program it to ignore records marked deleted instead of actually deleting them.
Table-ized A.I.
With newer advances such as Speedstep (or whatever they call it now), you can communicate to the servers that they are in a power outage mode and have them flip into a low power mode. Sure, they will run slower, but they won't go DOWN, and the resulting KW of power not being dissipated in the room will help keep things cooler, longer. Of course, in a colo, this means certain software that the server owner has to install. Better for this to be a hardware integration, with some type of network between the servers and the power management system and the cooling system. I know something like this would be fairly easy to implement, provided you had the right device in each server. I see performance adjustments which can downclock certain processors (laptops have had this for years), turn off hard drives, and blank all the monitors automatically (with an override of course).
Cool! Amazing Toys.
That's flatly incorrect. AC to DC conversion is a very simple and very efficient process.
I have no idea what you are talking about. It says what it says, exactly as I quoted it: "device/server"
What's more, no matter how you look at, it's simply NOT true.
A PSU would have to be 49% efficient or less, to output more heat itself than whatever device it is powering (Power==Heat). Meanwhile, even the very cheapest of junk PSUs are 60% efficient. I can't remember when I last saw a PSU that was any less efficient. Meanwhile, it's quite easy and inexpensive to purchase one of many PSUs that are 80% efficient or better, with a few exceeding 90%.
I'd say most do, but that's besides the point. No matter how many PSUs you have, they can't possibly be 60% efficient, and yet wasting more power than they are supplying. THAT'S WHAT THE PSU EFFICIENCY NUMBER MEANS.
No it couldn't. That 15% is not something you can get rid of in any way that I know of. It isn't caused by being AC, it's there because it costs some energy to convert from one voltage to another.
If you have some single power supply converting grid power into 48V DC, the 48V DC PSUs that convert into all the standard PC voltages will probably waste 15%+, and that's not including the losses from converting INTO 48V in the first place.
If you go to extremes, and standardize all PC hardware on a single voltage, then the losses will be in every device, and they will easily exceed 15%. Your motherboard will have to convert from a higher voltage down to whatever the CPU, chipset, and RAM needs. And you're still converting AC from the grid into low-voltage DC, which is certainly losing more than 15%, and then some more due to the high current in the electrical lines that now need to be massive. Not to mention that it still won't work, because every time a server turns on or off, the voltage will fluctuate slightly, which will potentially erase you RAM, cause your CPU to output garbage, cause your hard drive to spin down, etc., etc.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
I worked for a mid-sized business ISP a few years ago and we lost our HVACs. All 4 of them at the same time. The maintenance guy that came to do some routine crap was new and somehow completely fubar'd the entire system. We had 2 HVACS for cooling our two data centers and 2 on backup in case anything happened. He somehow managed to shut all 4 down and they absolutely refused to come back online.
It took about an hour before we had to begin shutting the least critical firewalls/servers/routers etc off. We let some pieces of equipment get to the point of melting before we unplugged them, because they were so critical and could be replaced for cheaper at a later time.
We all thought the company was done right then and there. Everyone stayed around the clock trying to think up plans. We had a data center in Minneapolis, 5 hours away that we could run all the big client equipment to, but other than that we were SOL.
Then someone made a few phone calls and managed to procure 8 portable air conditioners. The network engineers cut holes in the wall and ran ducts from the AC units to outside. We all took 2 hour shifts changing the water pans and keeping accurate temperature records throughout the weekend while the HVACs were being replaced.
What a nightmare that was... but we came out of it alright in the end. Didn't lose any major clients and didn't have to shuttle any equipment to minnesota. I bet the guy that got fired for screwin it all up will never work in the hvac industry again though. I still feel kinda bad for him.
You're nothing; like me.
The law is not an ass. No really.
The thing is for better or worse network centers have ended up in city centers, the further you are from those centers the more your connections cost.
note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register