How Google Spawned The 384-Chip Server

<i>Today, Mozilla is using SeaMicro’s older 512-core machines to handle downloads of its Firefox browser</i><p>Can anyone comment on the accuracy of this? "Handling downloads" is pretty vague, but still it seems like a pretty braindead job, and I know Mozilla is leveraging lots of mirrors and probably CDNs for this.

Note, as of yet due to its dependency on Intel's Atom line SeaMicro on only can't offer much memory per chip but they also can't offer parity or ECC, which is a much bigger deal killer for me.

So all those folks who always say "memory is cheap" and who make fun of others who write small conservative programs might not be so smart after all.<p>Because they can't run their "feature-rich" unconstrained applications on wimpy nodes. And thus they can't cut their employer's energy and real estate costs.<p>Why did Google abandon its plans to supply its own energy?

My favourite in this field was SiCortex, who were killed by a cashflow interruption at the start of the GFC.

Anyone else find it odd that seamicro.com doesn't give you any way to actually <i>buy</i> their product?

384 isn't that much you can easily get 500+ full fat cores in a full cab for HPC systems and that is leaving 2U for the infiband tor switch

Is nothing: in Soviet Russia, 384 servers chip YOU!<p>(I am so gonna get dinged, now :-))