Given by Paul Smith DoE at NSTC Committee Presentation on Sept 19,1996. Foils prepared Sept 19, 1996
Abstract * Foil Index for this file
This was stand alone presentation of PetaFlop Findings and Recommended Next Steps |
Audience was NSTC Committee on Computing Information and Communication |
This summarizes results of the series of Petaflop Workshops and Conference Events |
It Summarizes the case to move forward with the Federal Program |
This table of Contents
Abstract
I. Workshop series... background. |
II. Major findings & recommendations from the PetaFLOPS workshops. |
III. Key drivers for advanced computational capabilities beyond HPCC. |
IV. PetaFLOPS Architecture Point Designs & SW Design Studies. |
V. A National program concept. |
VI. Future actions to mold an R&D program. |
PetaFLOPS I
|
PetaFLOPS Bodega Bay Summer Study
|
PetaFLOPS Architecture Workshop, PAWS'96
|
PetaSOFT'96
|
Sponsoring Agencies |
NASA |
NSF |
DOE |
DARPA |
NSA |
BMDO |
t |
Private |
sector |
Academic |
Federal |
National |
Laboratories |
To identify immediate & future applications. |
To provide standard base (PetaFLOPS I) to measure advances in PetaFLOPS R&D. |
To identify critical enabling technologies. |
To assist technology directors to plan for future programs beyond HPCC. |
I. Workshop series... background: Coordinating Chairs |
Dr. Paul H. Smith.....................................................................General |
Special Assistant, Advanced Computing Technology |
U.S.. Department of Energy |
Dr. David Bailey .....................................................................Algorithms |
NASA/Ames Research Center |
Dr. Ian Foster ...........................................................................Software |
Division of Mathematics and Computer Science |
Argonne National Laboratory |
Prof.. Geoffrey Fox ............................................................................................Architecture |
Departments of Physics & Computer Science |
Prof.. Peter Kogge ...................................................................Architecture |
McCourtney Professor of Computer Science & Engineering |
University of Notre Dame |
I. Workshop series... background: Coordinating Chairs |
Prof.. Sidney Karin .......................................................................General |
Director for Advanced Computational Science & Engineering |
University of California, San Diego |
Dr Paul Messina ...........................................................................PetaFLOPS-I |
Director, Center for Advanced Computing |
California Institute of Technology |
Dr. Thomas Sterling .....................................................................Architecture |
Senior Scientist |
Jet Propulsion Laboratory |
Dr. Rick Stevens ..........................................................................Applications |
Director, Mathematics & Computer Science Division |
Argonne National Laboratory |
Dr. John Van Rosendale ..............................................................Point Design |
Division of Advanced Scientific Computing |
National Science Foundation |
PetaFLOPS possible; accelerate goals to 10 years. |
Many important application drivers exist. |
Memory dominant implementation factor. |
Cost, power & efficiency dominate. |
Innovation critical, new technology necessary. |
Layered SW architecture mandatory. |
Opportunities for immediate SW effort. |
New technology means paradigm shift.
|
Memory bandwidth. |
Latency. |
Software important. |
Closer relationship between architecture and programming is needed. |
Role of algorithms must improve. |
Conduct point design studies.
|
Develop engineering prototypes.
|
Start SW now, independent of HW. |
Develop layered software architecture for scalability and code reuse |
Explore algorithms for special purpose & reconfigurable structures. |
Support & accelerate R&D in paradigm shift technologies:
|
Perform detailed applications studies at scale. |
Develop petaFLOPS scale latency management. |
Nation's experts participated:
|
Strong need for computing at the high end. |
PetaFLOPS levels of performance are feasible. |
Preliminary set of goals for the next decade formulated with a PetaFLOPS system as the end product. |
II. Major Findings & Recommendations: |
Workshops Summaries. |
There are compelling applications that need that level of performance. |
PetaFLOPS levels of performance are feasible, but substantial research is needed. |
Private sector is not going to do it alone. |
TeraFLOPS machine architecture in hand. |
Programming still is explicit message passing. |
TeraFLOPS applications are coarse grain |
Latency management not showstopper for TeraFLOPS. |
Operating systems and tools provide relatively little support for the users |
Parallelism has to be managed explicitly |
Applications that require petaFLOPS can already be identified
|
The need for ever greater computing power will remain. |
PetaFLOPS systems are right step for the next decade |
Realistic 3-D Heart Models |
Genome comparisons |
Drug Design |
Real-time image compensation. |
Real-time atmospheric turbulence compensation. |
New materials |
Modeling US/World economy. |
Semiconductor component technology
|
Architecture
|
System software
|
There are compelling applications |
New architectures need to be investigated |
Component technologies need to developed |
Major advances are needed in system software and tools |
Industry is less likely than ever to push limits. |
Sponsored by NSF, DARPA and NASA |
Eight awards made of $100,000 each |
6 month study of architecture / |
SW environment / algorithms |
Reconfigurable OO architecture |
Processor in memory architecture |
Algorithmic focus |
Hierarchical design |
Aggressive cache only architecture |
Architecture for N-body problems |
Single quantum flux superconducting design |
Optical interconnect |
PetaFLOPS Applications which are grouped into sets with an interface to their own |
Problem Solving Environments |
Application Level or Virtual Problem Interface ADI |
Operating System Services |
Multi Resolution Virtual Machine Interfaces joining at lowest levels with |
Machine Specific Software |
Hardware Systems |
The mission critical applications |
Development of shared problem solving environments with rich set of application targeted libraries and resources |
Development of common systems software |
Programming environments from compilers to multi-level runtime support at the machine independent ADI's |
Machine specific software including lowest level of data movement/manipulation |
Start now on initial studies to explore the possible system architectures. |
These "PetaFLOPS software point studies" should be interdisciplinary involving hardware, systems software and applications expertise. |
Key, focused R&D must be explicitly funded |
Program is mostly D augmented with increases in R in HW/SW. |
Advanced systems designed and prototyped by the program. |
D will need strong central management. |
Applications tightly coupled with coordinated SW development groups. |
Target dozens of applications (not 100's) |
100's of programmers not thousands |
Deploy PF class systems < 10 years |
Starting in FY98 |
Multiple technology options |
New technologies and architectures |
Balance vendor vs direct development |
Open RFP for future systems |
Three "tracks" for illustration (might be more or less)
|
Deploy systems continuously |
Span generations with software model |
Pull with RFPs |
Push with technology investments |
Chip Interface:
|
Optical Networks:
|
Superconducting Memories:
|
Holographic Memories |
Natural Evolution Systems:
|
Special Purpose Architecture:
|
Hybrid Technology Architecture Development:
|
PetaFLOPS Languages:
|
Operating Systems:
|
Runtime Systems |
Algorithms to reduce latency associated with |
petaFLOPS scale: |
memory hierarchies & |
processor ensembles. |
Driver Applications:
|
SW level interface definitions |
Projection of performance requirements to lower levels (performance based design) |
Applications analysis wrt specific programming models (machines) |
Experimental testbeds simulated/modeled on existing MPP |
Need to invest in computing at the high end. |
PetaFLOPS level of performance are feasible. |
Private sector is not going to do it alone. |
Conduct detailed PetaFLOPS architecture design & simulation studies. |
Initiate early software development of layered architecture. |
Develop PetaFLOPS scale latency management |
Accelerate R&D in advanced technologies. |
Invent algorithms for special purpose and reconfigurable structures. |
The PetaFLOPS Frontier (Oct.. 96)
|
PetaFLOPS Algorithms Workshop (Apr.. 97) |
PetaFLOPS II Conference (Sep.. 97)
|
Engage community in establishing challenges, directions, topics for research |
Location: Williamsburg Hospitality House, Williamsburg, VA; April 20-25, 1997 |
Chair; David Bailey, NASA Ames |
Objectives:
|
Coordinate with High End Computing & Computation (HECC) Working Group. |
Develop Technical Approach --NOW |
Strategy for developing National Initiative. |
Multi-agency efforts. |
Federal agencies plan for FY'98 budget submission |