Table of Contents

HPC-IODC: HPC I/O in the Data Center Workshop

Logo

Managing scientific data at large scale is challenging for scientists but also for the host data center. The storage and file systems deployed within a data center are expected to meet users' requirements for data integrity and high performance across heterogeneous and concurrently running applications.

With new storage technologies and layers in the memory hierarchy, the picture is becoming murkier. To effectively manage the data load within a data center, I/O experts must understand how users expect to use these new storage technologies and what services they should provide in order to enhance user productivity. We seek to ensure a systems-level perspective is included in these discussions.

In this workshop we bring together I/O experts from data centers and application workflows to share current practices for scientific workflows, issues and obstacles for both hardware and the software stack, and R&D to overcome these issues.

The workshop content is built on two tracks with calls for papers/talks:

Contributions to both tracks are peer reviewed and require submission of the respective research paper or idea for your presentation via Easychair (see the descriptions below).

The workshop is held in conjunction with the ISC-HPC during the ISC workshop day. Note that the attendance of ISC workshops requires a workshop pass. See also our last year's workshop web page.

The HPC-IODC workshop is embedded into a full-day program for I/O that we organize with the team of the Workshop on Performance and Scalability of Storage Systems (WOPSSS) URL: http://wopsss.org/ We will build a program with a joint morning session with keynote talks and best papers and then diverge into two independent workshops in the afternoon.

Date Thursday June 28th, 2018
Venue Marriott Hotel, Frankfurt, Germany, Details about the ISC-HPC venue
Contact Dr. Julian Kunkel

This workshop is powered by the Virtual Institute for I/O and ESiWACE 1).

 

Agenda

The morning session is organized together with the WOPSSS.

After lunch, the big room is separated for the two workshops.

Organization

The workshop is organized by

Program committee

Participation

The workshop is integrated into ISC-HPC. We welcome everybody to join the workshop, including:

The call for papers and talks is already open. We accept early submissions, too, and typically proceed with them within 45 days. We particularly encourage early submission of abstracts such that you indicate your interest in submissions.

You may be interested to join our mailing lists at the Virtual Institute of I/O.

We especially welcome participants that are willing to give a presentation about the I/O of the representing institutions data center. Note that such presentations should cover the topics mentioned below.

Track: research papers

The research track accepts papers covering state-of-the-practice and research dedicated to storage in the datacenter. We accept short papers with up to 12 pages (excl. references) in LNCS format. Please see the instructions and templates for authors provided by Springer.

Our targeted proceedings are ISC's post-conference workshop proceedings in Springers LNCS. We use Easychair for managing the proceedings and PC interaction.

For accepted papers, the length of the talk during the workshop depends on the controversiality and novelty of the approach (the length is decided based on the preference provided by the authors and feedback from the reviewers). We also allow virtual participation (without attending the workshop personally). All relevant work in the area of data center storage will be able to publish with our joint workshop proceedings, we just believe the available time should be used best to discuss ambivalent topics.

Paper Deadlines

Review Criteria

The main acceptance criteria is the relevance of the approach to be presented – i.e., is the core idea worthwhile in the community to be discussed or novel. Since the camera-ready version of the papers is due after the workshop, we pursue two rounds of reviews:

  1. Acceptance for the workshop (as a talk)
  2. Acceptance as a paper *after* the workshop, this incorporates feedback from the workshop.

After the first review, all papers undergo a shepherding process.

Track: Talks by I/O experts

The topics of interest in this track include but are not limited to:

We also accept industry talks, given that they focus on operational issues on data centers and omit marketing.

We use Easychair for managing the acceptance and PC interaction. If you are interested to participate please submit a short (1/2 page) intended abstract of your talk together with a short Bio.

Deadlines for the submission of the abstract

Content

The following list of items should be tried to be integrated into a talk covering your data center, if possible. We hope your sites administrator will support you to gather the information with little effort.

  1. Workload characterization
    1. Scientific Workflow (give a short introduction)
      1. A typical use-case (if multiple are known, feel free to present more)
      2. Involved number of files / amount of data
    2. Job mix
      1. Node utilization (rel. to peak-performance)
  2. System view
    1. Architecture
      1. Schema of the client/server infrastructure
        1. Capacities (Tape, Disk, etc.)
      2. Potential peak-performance of the storage
        1. Theoretical
        2. Optional: performance results of acceptance tests.
      3. Software / Middleware used, e.g. NetCDF 4.X, HDF5, …
    2. Monitoring infrastructure
      1. Tools and systems used to gather and analyse utilization
    3. Actual observed performance in production
      1. Throughput graphs of the storage (e.g. from Ganglia)
      2. Metadata throughput (Ops/s)
    4. Files on the storage
      1. Number of files (if possible per file type)
      2. Distribution of file sizes
  3. Issues / Obstacles
    1. Hardware
    2. Software
    3. Pain points (what is seen as the biggest problem(s) and suggested solutions, if known)
  4. Conducted R&D (that aim to mitigate issues)
    1. Future perspective
    2. Known or projected future workload characterization
    3. Scheduled hardware upgrades and new capabilities we should focus on exploiting as a community
    4. Ideal system characteristics and how it addresses current problems or challenges
    5. what hardware should be added
    6. what software should be developed to make things work better (capabilities perspective)
    7. Items requiring discussion to work through how to address
1)
ESiWACE has received funding from the European Union’s Horizon 2020 Research and Innovation Programme under Grant Agreement No 675191