Feeds

China's Nebulae supercomputer - zero to second in 3 months

The perils of big-system assembly

Intelligent flash storage arrays

HPC Blog Those of you interested in what it really takes to bring up a massive system don't want to miss the "Lessons Learned Deploying the World's First GPU-Based Petaflop System" session.

In it, NVIDIA's senior hardware architect, Dale Southard, discusses his experience with China's Nebulae supercomputer - which, in addition to being the #2 system on the TOP500, was also probably the quickest big build of all time, at around three months total.

Southard, who describes himself as a professional debugger, has quite a track record with big systems. Before NVIDIA, he was at Lawrence Livermore, where he participated in a number of large builds (and probably has the scars to prove it). While the Nebulae super went from bare floor to petabyte processing in record time (about 90 days), it had its share of birthing pains.

In his session, Southard spent some time explaining the differences between small, medium and massive systems. According to him, the 'interesting times' begin in earnest when you move from thousand-node systems to something bigger.

The thousand-node system isn't trivial; it requires considerable - often custom - tooling for management and configuration tasks. But the bigger systems are a whole new world of complexity, mainly due to the fact that things that only rarely (if ever) go wrong on smaller systems malfunction frequently when you amass such a huge array of gear.

Southard related a story about a capacitor that blew up like a mini hand grenade, damaging other components as bits of it wormed their way into nooks and crannies. That's not something you see every day.

He also shared a laundry list of things to check out proactively before you begin big-system assembly. For example: make sure that all the systems have a common BIOS level and that they have the correct processors running at the right speed. When you're talking about such a large number of systems, even stringent quality control can let one or two inconsistent builds slip through. Catching these problems early will save countless hours of troubleshooting down the road.

The videos of the sessions aren't up yet, but I'm told that they should be posted by the end of the week. I'll put in links as soon as I get them... ®

Security for virtualized datacentres

More from The Register

next story
Just don't blame Bono! Apple iTunes music sales PLUMMET
Cupertino revenue hit by cheapo downloads, says report
The DRUGSTORES DON'T WORK, CVS makes IT WORSE ... for Apple Pay
Goog Wallet apparently also spurned in NFC lockdown
Cray-cray Met Office spaffs £97m on VERY AVERAGE HPC box
Only 250th most powerful in the world? Bring back Michael Fish
Microsoft brings the CLOUD that GOES ON FOREVER
Sky's the limit with unrestricted space in the cloud
'ANYTHING BUT STABLE' Netflix suffers BIG Europe-wide outage
Friday night LIVE? Nope. The only thing streaming are tears down my face
Google roolz! Nest buys Revolv, KILLS new sales of home hub
Take my temperature, I'm feeling a little bit dizzy
IBM, backing away from hardware? NEVER!
Don't be so sure, so-surers
prev story

Whitepapers

Why cloud backup?
Combining the latest advancements in disk-based backup with secure, integrated, cloud technologies offer organizations fast and assured recovery of their critical enterprise data.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The hidden costs of self-signed SSL certificates
Exploring the true TCO for self-signed SSL certificates, including a side-by-side comparison of a self-signed architecture versus working with a third-party SSL vendor.