Google Gives Behind-the-Scenes Peek

 
 
By Darryl K. Taft  |  Posted 2005-03-03 Email Print this article Print
 
 
 
 
 
 
 

In his EclipseCon keynote, Google VP Urs Hoelzle gives a glimpse into how the search company operates.

BURLINGAME, Calif.—At the EclipseCon 2005 conference here, a leading Google Inc. engineer gave a rare glimpse into the workings of the search powerhouse. In a keynote Wednesday titled "A Look Behind the Scenes at Google," Urs Hoelzle, vice president of engineering, essentially described the companys secret sauce as "the return of batch computing." Large numbers of cheap hardware, plus networking and intelligent software to support fault tolerance and other key functions, have gone a long way with the Mountain View, Calif., company, he said. Hoelzles talk also had a subplot: "the things behind search—how it works and how its organized."
Hoelzle described Googles mission as "to organize the worlds information and make it universally accessible and useful." This mission, he added, "drives a lot of the engineering we do."
With the Web consisting of 10 billion pages and the average page going 10 kilobytes, the total size is "many tens of terabytes," Hoelzle said. Yet, "its very big, but its actually tractable. We need a lot of computers and disks and networking and software." In fact, Google runs its system on commodity hardware running Linux, he said. "The underlying hardware is pretty damn cheap, but you have to build it into a system thats scalable," he said.
The primary components of the Google system are hardware, networking, distributed systems software, search algorithms, machine learning, information retrieval and user interfaces, Hoelzle said. He added that the hardware environment consists of racks and racks of 88 commodity PCs. "These things are cheap, and you can buy them anywhere," he said. "The problem is these things break. Things break everyday. If you have a thousand of these machines, expect to lose one a day. So you have to deal with that, and you better deal with that in an automated way. You deal with it in software by replication and redundancy." Google recently revealed its product formula. Click here to read more. Indeed, fault-tolerant software makes cheap hardware practical, Hoelzle said. And "sometimes things go very wrong," he said as he displayed a slide showing three fire trucks parked in front of a Google location. "I cant tell you exactly what happened, but it was not very good, and it was not just one machine going down." Yet, Hoelzle described Googles fault-tolerant solutions as "very robust," claiming the system "can tolerate massive failures." The company once lost 1,800 out of 2,000 machines in one environment, he said, but the operation continued to run—a bit slower, but it continued to work with 90 percent of its machines out of operation. Google uses an index, similar to a books index, which takes several days on hundreds of machines to compile, Hoelzle said. It has more than 8 billion Web documents and 1.1 billion images. Then Google uses its PageRank system for ranking and ordering the Web pages, he said. "Then we split them into pieces called shards, small enough to put on various machines. And we replicate the shards." So an incoming query would hit the Google Web server and then the index server and eventually a document server that contains copies of the Web pages Google downloads. Next Page: Managing the system.



 
 
 
 
Darryl K. Taft covers the development tools and developer-related issues beat from his office in Baltimore. He has more than 10 years of experience in the business and is always looking for the next scoop. Taft is a member of the Association for Computing Machinery (ACM) and was named 'one of the most active middleware reporters in the world' by The Middleware Co. He also has his own card in the 'Who's Who in Enterprise Java' deck.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel