File:Google’s First Production Server.jpg

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Original file(2,543 × 4,209 pixels, file size: 4.6 MB, MIME type: image/jpeg)

Summary

Google’s First Production Server

...with the hair pulled back, revealing a rack of cheap networked PCs, circa 1999.

Each level has a couple of PC boards slammed in there, partially overlapping. This approach reflects a presumption of rapid obsolescence of cheap hardware, which would not need to be repaired. Several of the PCs never worked, and the system design optimized around multiple computer failures.

According to Larry and Sergey, the beta system used Duplo blocks for the chassis because generic brand plastic blocks were not rigid enough.

We held an event at the Computer History Museum yesterday, and I noticed this new item in the collection. It pre-dates the Google Master Plan.

Licensing

Lua error in package.lua at line 80: module 'strict' not found.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current04:42, 4 January 2017Thumbnail for version as of 04:42, 4 January 20172,543 × 4,209 (4.6 MB)127.0.0.1 (talk)<blockquote> <p><b>Google’s First Production Server</b> </p> <p>...with the hair pulled back, revealing a rack of cheap networked PCs, circa 1999. </p> <p> Each level has a couple of PC boards slammed in there, partially overlapping. This approach reflects a presumption of rapid obsolescence of cheap hardware, which would not need to be repaired. Several of the PCs never worked, and the system design optimized around multiple computer failures. </p> <p> According to Larry and Sergey, the beta system used Duplo blocks for the chassis because generic brand plastic blocks were not rigid enough. </p> <p> We held an event at the Computer History Museum yesterday, and I noticed this new item in the collection. It pre-dates the Google Master Plan. </p> </blockquote>
  • You cannot overwrite this file.

The following 4 pages link to this file: