US DOE Sets Sights On 300 Petaflop Supercomputer

dcblogs writes U.S. officials Friday announced plans to spend $325 million on two new supercomputers, one of which may eventually be built to support speeds of up to 300 petaflops. The U.S. Department of Energy, the major funder of supercomputers used for scientific research, wants to have the two systems – each with a base speed of 150 petaflops – possibly running by 2017. Going beyond the base speed to reach 300 petaflops will take additional government approvals. If the world stands still, the U.S. may conceivably regain the lead in supercomputing speed from China with these new systems. How adequate this planned investment will look three years from now is a question. Lawmakers weren't reading from the same script as U.S. Energy Secretary Ernest Moniz when it came to assessing the U.S.'s place in the supercomputing world. Moniz said the awards "will ensure the United States retains global leadership in supercomputing." But Rep. Chuck Fleischmann (R-Tenn.) put U.S. leadership in the past tense. "Supercomputing is one of those things that we can step up and lead the world again," he said.

Comments

Re:Nice and all, but where's the beef?

[JanneM]

How should one go about getting a job programming a large supercomputer?

Become a researcher in a field that makes use of lots of computing power, then specialize in the math modeling and simulation subfields. Surprisingly often it's quite easy to get time on a system if you apply as a post-doc or even a grad student. Becoming part of a research group that develops simulation tools for others to use can be an especially good way.

Or, get an advanced degree in numerical analysis or similar and get hired by a manufacturer or an organization that builds or runs supercomputers. On one hand that'd give you a much more permanent job, and you'd be mostly doing coding, not working on your research; on the other hand it's probably a lot harder to get.

But ultimately, why would you want this? They're not especially magical machines. Especially today, when they're usually Linux based, and the system developers do all they can to make it look and act like a regular Linux system.

If you want to experience what it's like, try this: Install a 4-5 year old version of Red Hat on a workstation. Install OpenMP and OpenMPI, and make sure all your code uses either or both. Install an oddball C/C++ compiler. Access your workstation only via SSH, not directly. And add a job queue system that will semi-randomly let your app run after anything from a few seconds to several hours.