User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
events:2018:isc-io500 [2018/06/29 15:28] – [Agenda] kunkelevents:2018:isc-io500 [2018/06/30 18:25] kunkel
Line 10: Line 10:
  
 ===== Abstract ===== ===== Abstract =====
-Evolving and new storage technologies introduced over the last few years are causing increasing complexity for HPC data management. Hence, analyzing, comparing, or even predicting the performance of different HPC machines and storage systems has become more complicated. To address this challenge, the community has developed a new composite benchmark that has lead to the creation of the competitive IO-500 list. The IO-500 benchmark consists of several data and metadata benchmarks to identify performance boundaries for optimized and suboptimal applications. In addition to offering different ways to compare storage systems, the list collects detailed information about storage system design to help system designers make informed trade-offs when specifying new storage requirements. While the initial list contains only 9 systems, we expect a rapid growth in the second list.+ 
 +{{ :events:2018:isc-bof-ceremony.jpg?400|}} 
 + 
 + 
 +Evolving and new storage technologies introduced over the last few years are causing increasing complexity for HPC data management. Hence, analyzing, comparing, or even predicting the performance of different HPC machines and storage systems has become more complicated. To address this challenge, the community has developed a new composite benchmark that has lead to the creation of the competitive [[io500:list:18-06:start|IO-500 list]]. The IO-500 benchmark consists of several data and metadata benchmarks to identify performance boundaries for optimized and suboptimal applications. In addition to offering different ways to compare storage systems, the list collects detailed information about storage system design to help system designers make informed trade-offs when specifying new storage requirements. While the initial list contains only 9 systems, we expect a rapid growth in the second list.
  
 The development of the benchmark has been powered by the Virtual Institute for I/O (VI4IO), which provides a platform for I/O researchers and enthusiasts for exchanging information, fosters international collaboration in the field of HPC-I/O, and tracks the deployment of large storage systems. VI4IO provides a comprehensive data from sites, supercomputers and storage. This enables an in-depth analysis of various system characteristics. The development of the benchmark has been powered by the Virtual Institute for I/O (VI4IO), which provides a platform for I/O researchers and enthusiasts for exchanging information, fosters international collaboration in the field of HPC-I/O, and tracks the deployment of large storage systems. VI4IO provides a comprehensive data from sites, supercomputers and storage. This enables an in-depth analysis of various system characteristics.
Line 20: Line 24:
   * **The IO-500** -- //John Bent//    * **The IO-500** -- //John Bent// 
   * **Procuring small HPC storage using IO-500 benchmark** -- //George Markomanolis// -- {{ :events:2018:isc-bof-procurement.pdf |Slides}}   * **Procuring small HPC storage using IO-500 benchmark** -- //George Markomanolis// -- {{ :events:2018:isc-bof-procurement.pdf |Slides}}
-  *  **VI4IO** -- //Julian Kunkel// -- {{ :events:2018:isc-bof-vi4io.pdf |Slides}}+  *  **The Virtual Institute for I/O** -- //Julian Kunkel// -- {{ :events:2018:isc-bof-vi4io.pdf |Slides}}
   * **The new IO-500 list** -- //John Bent// -- {{ :events:2018:isc-bof-reveal.pdf |Slides}}   * **The new IO-500 list** -- //John Bent// -- {{ :events:2018:isc-bof-reveal.pdf |Slides}}
 +  * **Features of the new IO-500 list** -- //Julian Kunkel// -- Please visit: https://www.vi4io.org/io500/radar for a live demo.
   * **Moderated discussion** -- //Jay, Julian, John//   * **Moderated discussion** -- //Jay, Julian, John//