Here we will discuss the latest thoughts on what will be involved in building computing hardware to function at the peta(Fl)ops level. Please feel free to contact the editoral board with any updates or additional information that is relevant.
The organization of this material is as follows:
Besides updating the above material as time goes on, we will also add additional discussion areas dealing with key system issues such as most appropriate performance metrics, I/O, backing storage, packaging, etc.
Thus, one PetaFLOPS of performance would require 1 PB of accessible memory and 8 PB per second between that memory and the hardware performing the computations. Both of these heavily drive the overall parameters of any PetaFLOPS machine, regardless of architecture. In the 1993 PetaFLOPS Workshop, the surfacing of these two metrics (particularly storage) caused the applications subgroup to come to the conclusion that there is an important class of problems (basically three dimensional plus time simulations) where a rule of N GF requiring N**3/4 GB might be more appropriate. This would translate into a useable PetaFLOPS system with a mere 32 TB of main memory - a 30X reduction in needed memory.
Curators: Michele O'Connell (Michele.OConnell@hq.nasa.gov), Lawrence Picha (Larry.Picha@hq.nasa.gov),