Software Roadmap to Plug and Play Petaflop/s
Abstract
In the next five years, the DOE expects to build systemsthat approach a petaflop in scale. In the near term (two years), DOE willhave several near-petaflops systems that are 10 percent to 25 percent ofa peraflop-scale system. A common feature of these precursors to petaflopsystems (such as the Cray XT3 or the IBM BlueGene/L) is that they rely onan unprecedented degree of concurrency, which puts stress on every aspectof HPC system design. Such complex systems will likely break current bestpractices for fault resilience, I/O scaling, and debugging, and evenraise fundamental questions about languages and application programmingmodels. It is important that potential problems are anticipated farenough in advance that they can be addressed in time to prepare the wayfor petaflop-scale systems. This report considers the following fourquestions: (1) What software is on a critical path to make the systemswork? (2) What are the strengths/weaknesses of the vendors and ofexisting vendor solutions? (3) What are the local strengths at the labs?(4) Who are other key players who will play a role and canhelp?
- Authors:
- Publication Date:
- Research Org.:
- Lawrence Berkeley National Lab. (LBNL), Berkeley, CA (United States)
- Sponsoring Org.:
- USDOE Director. Office of Science. Office of AdvancedScientific Computing Research
- OSTI Identifier:
- 910585
- Report Number(s):
- LBNL-59999
R&D Project: KN6011; BnR: YN0100000; TRN: US200724%%258
- DOE Contract Number:
- DE-AC02-05CH11231
- Resource Type:
- Technical Report
- Country of Publication:
- United States
- Language:
- English
- Subject:
- 99; DESIGN; PROGRAMMING; SUPERCOMPUTERS; supercomputer high performance computing scalablesoftware
Citation Formats
Kramer, Bill, Carter, Jonathan, Skinner, David, Oliker, Lenny, Husbands, Parry, Hargrove, Paul, Shalf, John, Marques, Osni, Ng, Esmond, Drummond, Tony, and Yelick, Kathy. Software Roadmap to Plug and Play Petaflop/s. United States: N. p., 2006.
Web. doi:10.2172/910585.
Kramer, Bill, Carter, Jonathan, Skinner, David, Oliker, Lenny, Husbands, Parry, Hargrove, Paul, Shalf, John, Marques, Osni, Ng, Esmond, Drummond, Tony, & Yelick, Kathy. Software Roadmap to Plug and Play Petaflop/s. United States. https://doi.org/10.2172/910585
Kramer, Bill, Carter, Jonathan, Skinner, David, Oliker, Lenny, Husbands, Parry, Hargrove, Paul, Shalf, John, Marques, Osni, Ng, Esmond, Drummond, Tony, and Yelick, Kathy. 2006.
"Software Roadmap to Plug and Play Petaflop/s". United States. https://doi.org/10.2172/910585. https://www.osti.gov/servlets/purl/910585.
@article{osti_910585,
title = {Software Roadmap to Plug and Play Petaflop/s},
author = {Kramer, Bill and Carter, Jonathan and Skinner, David and Oliker, Lenny and Husbands, Parry and Hargrove, Paul and Shalf, John and Marques, Osni and Ng, Esmond and Drummond, Tony and Yelick, Kathy},
abstractNote = {In the next five years, the DOE expects to build systemsthat approach a petaflop in scale. In the near term (two years), DOE willhave several near-petaflops systems that are 10 percent to 25 percent ofa peraflop-scale system. A common feature of these precursors to petaflopsystems (such as the Cray XT3 or the IBM BlueGene/L) is that they rely onan unprecedented degree of concurrency, which puts stress on every aspectof HPC system design. Such complex systems will likely break current bestpractices for fault resilience, I/O scaling, and debugging, and evenraise fundamental questions about languages and application programmingmodels. It is important that potential problems are anticipated farenough in advance that they can be addressed in time to prepare the wayfor petaflop-scale systems. This report considers the following fourquestions: (1) What software is on a critical path to make the systemswork? (2) What are the strengths/weaknesses of the vendors and ofexisting vendor solutions? (3) What are the local strengths at the labs?(4) Who are other key players who will play a role and canhelp?},
doi = {10.2172/910585},
url = {https://www.osti.gov/biblio/910585},
journal = {},
number = ,
volume = ,
place = {United States},
year = {Mon Jul 31 00:00:00 EDT 2006},
month = {Mon Jul 31 00:00:00 EDT 2006}
}