Light Reading Mobile – Telecom News, Analysis, Events, and Research

Opinion  

Google's 10-GigE Assault

November 16, 2007 | Andrew Schmitt |

It is our opinion that Google has designed and deployed home-grown 10-Gbit/s Ethernet switches as part of a secret internal initiative that was launched when it realized commercial options couldn't meet the cost and power consumption targets required for their data centers.

This decision by Google, while small in terms of units purchased, is enormous in terms of the disruptive impact it should have on 10-Gbit/s Ethernet switching equipment providers and their component supply chains. It is as if a MACHO just arrived in the Enterprise networking business and the orbits of the existing satellites have begun to shift without observers knowing why - until now.

We were watching shipments of SFP+ components for 10-Gbit/s Ethernet in the market but simply couldn't account for their end destination - sort of an optical component dark matter problem. After a great deal of investigation we have reached the following opinion:

Through conversations with multiple carrier, equipment, and component industry sources, we have confirmed that Google has designed, built, and deployed homebrewed 10-Gbit/s Ethernet switches for providing server interconnect within their data centers. This is very similar to Google's efforts to build its own server computers. Google realized that, because its computing needs were very specific, it could design and build computers that were cheaper and lower power than off-the-shelf alternatives. The decision to do so had a profound impact on server architecture and influenced the market's move to lower power density solutions that Sun Microsystems Inc., Intel Corp., and Advanced Micro Devices now embrace.

It now appears that the process Google trailblazed in the server computing market will repeat itself in the enterprise switching market. Given the relative dearth of low-cost 10-GigE switching solutions, it isn't surprising to see Google revisit this approach.

Read the rest at The Nyquist Condition.

— Andrew Schmitt, Nyquist Capital



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Related Content
White Papers SPONSORED CONTENT
Featured