BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Denver
X-LIC-LOCATION:America/Denver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:MDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20260422T000713Z
LOCATION:605
DTSTART;TZID=America/Denver:20231112T153000
DTEND;TZID=America/Denver:20231112T155500
UID:submissions.supercomputing.org_SC23_sess434_ws_ftxs106@linklings.com
SUMMARY:Optimizing Write Performance for Checkpointing to Parallel File Sy
 stems Using LSM-Trees
DESCRIPTION:Serdar Bulut and Steven A. Wright (University of York, England
 )\n\nThe widening gap between compute and I/O performances on modern HPC s
 ystems means that writing checkpoints to a parallel file system for fault 
 tolerance is fast becoming a bottleneck to high-performance. It is therefo
 re vital that software is engineered such that it can achieve the highest 
 proportion of available performance on the underlying hardware; and this i
 s a burden often carried by I/O middleware libraries. In this paper, we ou
 tline such an I/O library based on a Log-structured Merge Tree (LSM-Tree),
  not just for metadata, but also scientific data. We benchmark its perform
 ance using the IOR benchmark, demonstrating 2.4 to 76.7x better performanc
 e than alternative file formats, such as ADIOS2, HDF5, and IOR baseline wh
 en running on a Lustre Parallel File System. We further demonstrate that w
 hen our LSM-Tree I/O library is used as a storage-layer for ADIOS2, the re
 sulting I/O library still outperforms the default ADIOS2 implementation by
  1.5x.\n\nTag: Fault Handling and Tolerance, Large Scale Systems\n\nRegist
 ration Category: Workshop Reg Pass\n\nSession Chairs: John Daly (US Depart
 ment of Defense), Scott Levy (Sandia National Laboratories), and Keita Ter
 anishi (Oak Ridge National Laboratory (ORNL))\n\n
END:VEVENT
END:VCALENDAR