Google throws open doors to its top-secret data center
wired.com
wired.com
In fact, while much of the content in the article has been written about before, it's still probably 2-3 years or more behind where Google is actually at. I left in 2010 and did't read about anything I had not experienced.
It was pretty funny at the time but the lesson wasn't lost on me: With competition, get ahead, stay ahead, and have things already done and implemented so you can announce big accomplishments when it's strategic for you.
There's a great graph in "Toyota Kata" that shows per-worker productivity of major car companies for the last several decades. They all rise together for the early part of the graph. In the 60s, the American car companies level off; Toyota keeps growing. They focused on continuous improvement, while American car companies floundered.
The really interesting part of this to me is that it's rooted in a philosophical difference. Toyota was started and run by engineers. The American car companies gave birth to the MBA approach to business. Engineers naturally seek improvement; MBAs seek profit.
Google is one of the few major companies with a philosophical background like Toyota's. It's run by nerds. Their goal isn't to increase shareholder value; it's to build great stuff and organize the world's information. Like Toyota, by following their vision, they have generated vast profits and dominated their industry.
Just curious, is that still valid or has the company been overrun with "Samsungnitis".
You know, stay one step behind, clone and ship mass produced junk in different price ranges?
If I'm not mistaken (Please correct if so); "Lean" is pretty much the "toyota improvement strategy" adapted to the software industry.
I'd recommend reading a little about lean, kanban and/or agile "methods" in general. Mary Poppendieck's a name to look for
I still wonder how they can manage to build affordable, reliable cars that last for years, while many expensive car makers have absurdly high failure rates.
Toyota's approach focuses on value from the customer perspective. So all defects are seen as waste, and are targeted for elimination.
The MBA approach just looks at P&L. Which is why they concealed the Pinto's tendency to explode; it was cheaper to pay the lawsuits than to fix people's tanks. Nevermind that many more people would die without the recall; that wasn't relevant to increasing shareholder value.
Another good example comes at the beginning of Bob Lutz's "Car Guys vs Bean Counters". Lutz, a car lover and an automotive exec for decades, once fixed a problem with transmission manufacturing. The problem was causing a lot of people's cars to die right after the warranty expired. He got yelled at because it blew a hole in their revenue projections; they were looking forward to a lot of highly profitable transmission repairs.
Toyota can make those reliable cars because they see every worker not just as a meat robot, but as a brain that should be engaged in eliminating waste. MBA thinking looks at slow order periods as a time to cut labor costs. Toyota, cognizant of how much they have invested in their workers, looks it as a time for training, plant improvement, and other value-creating activities.
http://en.wikipedia.org/wiki/W._Edwards_Deming#Deming_philos...
One of the details which I find highly relevant to software and, particularly, operations is rejecting the mindset of dealing with failure by finding someone to blame and instead changing the system so that one person can't inadvertently cause a failure. I see this a lot with massive ops run books which require humans to repeatedly perform complex tasks without mistake rather than automating it and regularly testing your automation.
Even if this is taken as a fact, I don't see how it explains why American car companies level off. It's not like potential profit is bounded but potential improvement isn't.
So, for example, an MBA can increase profits by cutting R&D. Or by cutting costs in a way that harms product quality. The company will do well for a while because it takes a while for things like reputation and mindshare to decline. You can hide the declines for longer by investing more in promotion.
The engineer-style approach, in contrast, is to focus on cutting waste rather than cost. This is a high art in the Toyota Production System:
http://en.wikipedia.org/wiki/Muda_%28Japanese_term%29
I don't know that the leveling off is a necessary consequence of the MBA approach. But it's certainly what I've seen, and it makes some intuitive sense. Given that some ways to increase profit improve productivity and some harm it, it's plausible that all the cheap ways to improve productivity would be exhausted early in the MBA approach.
I also think the MBA approach can lead you into a local maximum that's pretty screwed up:
http://www.thisamericanlife.org/radio-archives/episode/403/n...
That's a great radio story about NUMMI, one of GM's worst plant that under the Toyota system became one of the best.
Google is another good example. They didn't seek out data center "best practices". They radically bested the competition, proceeding one step at a time, with careful attention to what they needed. In an MBA analysis, that would be seen as spending a lot of money on risky R&D with no obvious ROI. In fact, they'd want to re-task all those expensive engineer brains to something more directly related to revenue. And probably drop the quality of the ops staff as a money-saving measure.
It's only when the years of patient engineer-style optimization add up to an insurmountable lead that it looks good in a B-school spreadsheet.
What if they just plateaued and didn't really go beyond what you had done when you were there, and this is totally accurate to today?
[1] Platforms is the group at Google that designs and builds the technology that goes into the data-centers.
http://www.wired.com/wiredenterprise/2012/10/ff-inside-googl...
EDIT:
The article talks about Google's impressive technical achievements. But there's a lot of energy that's wasted in industry. I don't mean "used inefficiently" (although that's bad too); I mean actually wasted.
I used to work at a tiny electronic sub-contracting factory. The morning shift would arrive, turn on the air compressor (2 KW), the reflow ovens (10 KW and 12 KW); and the other machines (about 7 KW).
But they'd do that even if the machines were not going to be running. All these KW were being used for no reason at all. And the machines are pretty inefficient anyway. (One of the owners thought powered machines looked more impressive. Energy costs were included in the rent so there was no incentive to think about when the machines were on or off. )
Counting that waste across all the tiny factories in the world, and including all the waste in offices - it's quite a lot.
Fundamentally, all cooling is the process of transferring heat from one place to another.
but searching briefly just now I can't find any followup beyond the announcement, not clear if it became reality.
Waste is operating any equipment when not needed, regardless of its internal efficiency.
Another example: Using an incandescent light bulb instead of an LED is inefficient - but leaving either on when not needed is wasteful.
Not always the case, but I can assure you that in California, office heating demands are very, very low.
Otherwise you are pretty much out of luck - The efficiency of energy extraction from a heat engine is thermodynamiclly limited by the difference between the hot and cold sides. And trying to transport it any significant distance ends up being more trouble than its worth as pumping water gets energy intensive very quickly (and air has terrible heat capacity.)
1-sqrt(294/322) = 4.4%
So, for every 100 watts of heat, you could recover 4.4 watts of power.
The only data stored there is probably Doodles...
They should probably contract a couple Disney Imagineers and do it right. They could benefit from the the humanizing effects and even create a quirky, niche destination in the process. Hell, throw in an "Android Experience" showroom and it'd probably even have legitimate commercial value.
I wonder why they've mirrored the image (the left side is quite clearly the right side flipped--take a look at the machine identifier labels). What's being hidden?
[1] http://www.google.com/about/datacenters/gallery/#/all/12
What if Google was tasked with building an orbiting datacenter? How about a Dyson ring, or sphere? How would you do it?
If we were to use all matter in the solar system for commodity linux hardware, how much gmail storage would I get? How many flops? And what sorts of computation could you do on this monster?
Please answer! This should be fun...
First off, building a datacenter in space would not be cheap. It costs around $25,000 to send a kilogram of equipment into a geostationary orbit. [1] So let assume we were to use Dell PowerEdge C1100. Each server costs $14,000 and weights 18kg. [2] This means for each server sent in orbit, you could buy 32 extra ones on Earth.
Then, there is the issue of cooling. Although outer space is really cold, its vacuum prevents the heat generated by the machines from being dissipated quickly. Controlling the temperature of a such datacenter would be a very interesting engineering challenge.
And then how would you power this datacenter? Converting the excess heat back into electricity could be an interesting option. But most likely, it would need a lot of solar panels. This would make the datacenter cheap to run once built, but the upfront costs would be enormous.
And we haven't talked about speed and reliability yet. Since the signal would need to travel about 35,000 km from the geostationary orbit to reach us, communications between Earth and the datacenter would have significant delays. Even at the speed of light, the minimum round trip time would be about 250 milliseconds if we ignore all other possible sources of delay.
The hostile space weather would also make it pretty hard to run servers reliability. Radiations would destroy electronics, caused bit to flip randomly and do all bunch of fun stuff to the equipment.
But... anyhow! Let's assume anyway that by some magical work of science and Google engineering, we figure ways to manufacture a datacenter directly space for almost nothing by mining the Moon, discover some amazing thermoelectric generators with near 100% efficiency and space shields that blocks almost all radiations.
So back our previous example, a high performance PowerEdge gives us up to about 300 GFLOPS of computing power, 192 GB of RAM and 12 TB of storage.
Now if we were to convert the total mass of the Moon (7.34767309 × 10²² kg) into one monstrous datacenter, this would give us about 4.0 × 10²¹ servers. It would gives us a whooping 1.2 billions YottaFLOPS (or put differently, 1.2 × 10³³ FLOPS) of compute madness, 0.8 billions YottaBytes and 49 billions YottaBytes of storage. This monster would consume about the equivalent of 1% of the Sun's total power output.
[1]: http://www.futron.com/upload/wysiwyg/Resources/Whitepapers/S... [2]: http://www.dell.com/us/enterprise/p/poweredge-c1100/pd#TechS...
If you stick a heatsink on equipment in space, there's no air that can move the heat away, since space is mostly empty. You'll bleed off some through infrared radiation, but that's not going to be enough.
Some follow up questions: let's assume that we need to move 10^10 yottabytes from the MoonPC to the earth. How do we do it? What's the fastest we could do it without transfering so much heat that it melts either end of the connection?
Maybe they don't want you to see inside.
How did Google do this time? Pretty well. Despite the outages in the corporate network, executive chair Eric Schmidt was able to run a scheduled global all-hands meeting. The imaginary demonstrators were placated by imaginary pizza.
How does one decide what will placate imaginary demonstrators? Who calls them off?
You're right -- those PUE numbers from the article were talking about their PUE at the time. Google's 2012 average PUE across all facilities was 1.12/1.13 with a minimum PUE of 1.09/1.10.
Also, Google puts enormous care into the process of calculating PUE since it's kind of black art and if you aren't careful you'll leave out some aspect of your operation that will mislead you into thinking your PUE is lower than it is.
Maybe Google really is Sun v2 ("We are the dot in dot-com" == "Where the Internet lives").
http://www.google.com/about/datacenters/gallery/
I thought GWT was designed to "compile" rendered pages for a wide variety of browsers and permutations of configurations?
The pictures are very pretty, but that's really awful of them to release a PR site like this, and force users into using JavaScript.
Unforgivable.