BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20250626T234542Z
LOCATION:B309
DTSTART;TZID=America/New_York:20241117T162000
DTEND;TZID=America/New_York:20241117T162500
UID:submissions.supercomputing.org_SC24_sess736_ws_pdswwip110@linklings.co
 m
SUMMARY:Exploring the Proactive Data Containers Runtime System in VAST - A
  Case Study
DESCRIPTION:Jean Luca Bez (Lawrence Berkeley National Laboratory (LBNL)) a
 nd Suren Byna (The Ohio State University, Lawrence Berkeley National Labor
 atory (LBNL))\n\nProactive Data Containers (PDC) is an object-centric runt
 ime metadata and data management system designed for transparent, asynchro
 nous, and autonomous data movement, taking advantage of the complex memory
  and storage hierarchy. We have previously explored PDC's performance and 
 scalability with a traditional Lustre-based storage backend. Understanding
  PDC's behavior on novel storage solutions like VAST offers the chance to 
 support cross-facility and multi-filesystem deployment for complex scienti
 fic analysis while preserving the key characteristics PDC was designed to 
 attain. In this work-in-progress, we share our initial scalability results
  of PDC operations when running atop of a VAST data system.\n\nTag: Data M
 ovement and Memory, I/O, Storage, Archive\n\nRegistration Category: Worksh
 op Reg Pass\n\nSession Chairs: Suren Byna (The Ohio State University, Lawr
 ence Berkeley National Laboratory (LBNL)); Dean Hildebrand (Google LLC); A
 nthony Kougkas (Illinois Institute of Technology, Argonne National Laborat
 ory (ANL)); Jay Lofstead (Sandia National Laboratories, University of New 
 Mexico); and Bing Xie (Microsoft Corporation)\n\n
END:VEVENT
END:VCALENDAR