FAST '24 Call for Papers

Sponsored by USENIX in cooperation with ACM SIGOPS.

The 22nd USENIX Conference on File and Storage Technologies (FAST '24) will take place on February 27–29, 2024, at the Hyatt Regency Santa Clara in Santa Clara, CA, USA.

Important Dates

  • Paper submissions due: Thursday, September 21, 2023, 11:59 pm PDT
  • Author response period begins: Monday, November 27, 2023
  • Author response period ends: Wednesday, November 29, 2023, 11:59 pm PST
  • Notification to authors: Friday, December 8, 2023
  • Final paper files due: Monday, January 29, 2024

Conference Organizers

Program Co-Chairs

Xiaosong Ma, Qatar Computing Research Institute, Hamad Bin Khalifa University
Youjip Won, Korea Advanced Institute of Science and Technology (KAIST)

Program Committee

George Amvrosiadis, Carnegie Mellon University
Ali Anwar, University of Minnesota
Oana Balmau, McGill University
John Bent, Seagate
Janki Bhimani, Florida International University
Angelos Bilas, University of Crete and FORTH
Ali R. Butt, Virginia Tech
Andromachi Chatzieleftheriou, Microsoft Research
Young-ri Choi, UNIST (Ulsan National Institute of Science and Technology)
Angela Demke Brown, University of Toronto
Peter Desnoyers, Northeastern University
Aishwarya Ganesan, University of Illinois at Urbana–Champaign and VMware Research
Ashvin Goel, University of Toronto
Haryadi Gunawi, University of Chicago
Dean Hildebrand, Google
Yu Hua, Huazhong University of Science and Technology
Jian Huang, University of Illinois at Urbana–Champaign
Jooyoung Hwang, Samsung Electronics
Jinkyu Jeong, Yonsei University
Sudarsun Kannan, Rutgers University
Sanidhya Kashyap, EPFL
Youngjin Kwon, Korea Advanced Institute of Science and Technology (KAIST)
Patrick P. C. Lee, The Chinese University of Hong Kong (CUHK)
Sungjin Lee, Daegu Gyeongbuk Institute of Science and Technology (DGIST)
Cheng Li, University of Science and Technology of China
Youyou Lu, Tsinghua University
Peter Macko, MongoDB
Changwoo Min, Igalia
Beomseok Nam, Sungkyunkwan University
Sam H. Noh, Virginia Tech
Raju Rangaswami, Florida International University
Jiri Schindler, IonQ
Phil Shilane, Dell Technologies
Keith A. Smith, MongoDB
Vasily Tarasov, IBM Research
Eno Thereska, Alcion, Inc.
Carl Waldspurger, Carl Waldspurger Consulting
Wen Xia, Harbin Institute of Technology
Gala Yadgar, Technion—Israel Institute of Technology
Ming-Chang Yang, The Chinese University of Hong Kong (CUHK)

Work-in-Progress/Posters Co-Chairs

Ali R. Butt, Virginia Tech
Young-ri Choi, UNIST (Ulsan National Institute of Science and Technology)

Test of Time Awards Committee

Geoff Kuenning, Harvey Mudd College
Raju Rangaswami, Florida International University

Mentoring Co-Chairs

Aishwarya Ganesan, University of Illinois at Urbana–Champaign and VMware Research
Dean Hildebrand, Google

Steering Committee

Marcos K. Aguilera, VMware Research
Ashvin Goel, University of Toronto
Casey Henderson-Ross, USENIX Association
Dean Hildebrand, Google
Dalit Naor, The Academic College of Tel Aviv–Yaffo
Sam H. Noh, Virginia Tech
Don Porter, The University of North Carolina at Chapel Hill
Raju Rangaswami, Florida International University
Carl Waldspurger, Carl Waldspurger Consulting
Gala Yadgar, Technion—Israel Institute of Technology


The 22nd USENIX Conference on File and Storage Technologies (FAST '24) brings together storage-system researchers and practitioners to explore new directions in the design, implementation, evaluation, and deployment of storage systems. The program committee interprets "storage systems" broadly: submissions on low-level storage devices, distributed storage systems, and information management are all of interest. The conference will consist of technical presentations including refereed papers, and poster sessions. As with recent conferences, several papers may be selected for fast tracking to a special section/issue of ACM’s Transaction on Storage journal (ACM TOS)


Topics of interest to FAST should include files and/or storage, and may overlap with other topics including, but not limited to:

  • Archival systems
  • Auditing and provenance
  • AI for storage and storage for AI
  • Big data, analytics, and data sciences
  • Caching, replication, and consistency
  • Cloud, multi- and hybrid-cloud environments
  • Data deduplication
  • Database storage
  • Distributed and networked storage (wide-area, grid, peer-to-peer)
  • Emerging memory hierarchy design
  • Empirical evaluation
  • Experience with deployed systems
  • File system design
  • HPC systems (including parallel I/O)
  • Key-value and NoSQL storage
  • Management
  • Memory-only storage systems
  • Mobile, personal, embedded, and home storage
  • Networking
  • Novel and emerging storage technologies (e.g., DNA storage)
  • Performance and QoS
  • Power-aware storage architectures
  • RAID and erasure coding
  • Reliability, availability, and disaster tolerance
  • Search and data retrieval
  • Security

In evaluating the fit of a paper for FAST, a key ingredient is the design of storage software. A paper with only hardware-level contributions will be out-of-scope; a paper could be brought into scope for FAST by demonstrating for example how software can leverage novel hardware.

Submission Instructions

Please submit your paper by 11:59 pm PDT on September 21, 2023, in PDF format via the submission form. Do not email submissions. There is no separate deadline for abstract submissions.

  • The complete submission must be no longer than 12 pages excluding references. There is no short-paper category. The program committee values conciseness: if you can express an idea in fewer pages than the limit, do so. Supplemental material may be added as a single separate file without page limits. However, the reviewers are not required to read or consider such material. Content that should be considered to judge the paper is not supplemental and counts toward the page limit.
  • Papers must be typeset on U.S. letter-sized pages in two columns using 10-point Times Roman font on 12-point leading (single-spaced), within a text block 7" wide by 9" deep.
  • Labels, captions, and other text in figures, graphs, and tables must use font sizes that, when printed, do not require magnification to be legible. References must not be set in a smaller font. Submissions that violate these requirements will not be reviewed. Limits will be interpreted strictly. No extensions will be given for reformatting.
  • A LaTeX template and style file are available on the USENIX templates page.
  • Double-blind policy: Authors must not be identified in the submissions, either explicitly or by implication. To refer to your previous work, consider it as written by a third party. Do not say "reference removed for blind review." Supplemental material must be anonymized. Submissions violating anonymization rules will not be considered for review. If you are uncertain about how to anonymize your submission, please contact the program co-chairs,, well in advance of the submission deadline.
  • Prior Workshop Paper Policy: If a submission extends a prior workshop paper, please include an anonymized copy of the workshop paper in the submission field. This should be the same as the published version, with any identifying information removed.
  • Simultaneous submission of the same work to multiple venues, submission of previously published work, or plagiarism constitutes dishonesty or fraud. USENIX, like other scientific and technical conferences and journals, prohibits these practices and may take action against authors who have committed them. See the USENIX Conference Submissions Policy for details.
  • If you are uncertain whether your submission meets USENIX's guidelines, contact the program co-chairs,, or the USENIX office,
  • Papers accompanied by nondisclosure agreement forms will not be considered.
  • Submissions should abide by the Conflict Identification guidelines (see below).

The program committee and external reviewers will judge papers on technical merit, significance, relevance, and presentation. Research papers on new and unexplored problems are encouraged. A good research paper:

  • addresses a significant problem;
  • presents an interesting, compelling solution;
  • demonstrates the benefits and drawbacks of the solution;
  • draws appropriate conclusions using sound experimental methods;
  • clearly describes what the authors have done; and
  • clearly articulates the advances beyond previous work.

Program committee members, USENIX, and the broader community generally value a paper more highly if it clearly defines and is accompanied by artifacts not previously available. These artifacts may include traces, original data, source code, or tools developed as part of the submitted work.

Blind reviewing of all papers will be done by the program committee, assisted by outside referees when necessary. Accepted papers will be shepherded by a member of the program committee.

Deployed-Systems Papers

In addition to papers that describe original research, FAST '24 also solicits papers that describe real operational systems, including systems currently in production. Such papers should address experience with the practical design, implementation, analysis, deployment, or operation of such systems. We encourage the submission of papers that disprove or strengthen existing assumptions, deepen the understanding of existing problems, and validate known techniques in environments in which they were never before used or tested, with preference given to experimental results based on production data. Deployed-system papers will be treated similarly to other papers for publication purposes; they need not present new ideas or results to be accepted, but should offer useful guidance to practitioners.

A good deployed-system paper:

  • clearly articulates lessons learned from deploying in production;
  • describes an operational system of broad interest;
  • discusses practical problems encountered in production; and
  • supports the lessons with appropriate evidence, potentially including statistical data from the actual deployment, empirical evaluation of the system (on production platforms rather than small testbeds), and anecdotes.

For deployed systems papers, the title should be prefixed with "Deployed System: ", followed by the title. Authors must also indicate in the submission form that they are submitting a deployed-system paper.

Double-blind Policy for Deployed-system Paper: All submissions for FAST '24 are required to follow the double-blind policy (see above). However, with deployed-system papers, the product or company described in the paper need not be anonymized (unlike author names).

Author Response Period

FAST '24 will allow authors to respond to reviews prior to final decision, according to the schedule above. Authors must limit their response to correcting factual errors in the reviews, to addressing questions posed by reviewers, and to clarifying the ideas in the paper. Responses may include new experiments and data in response to a reviewer request. Responses are optional and limited to 1000 words. For the first time, FAST will be enforcing a hard limit on the length of the author response for fairness and for reducing workload (for both authors and reviewers): exceeding the word limit will impact a paper negatively.

Conflict Identification

Upon submitting your paper, authors must indicate conflicts with PC members. A conflict exists in one of the following cases:

Institution: You are currently employed at the same institution, have been previously employed at the same institution within the past two years, or are going to begin employment at the same institution. A completed internship does not constitute an institutional conflict.

Advisor/Advisee: Doctoral thesis advisor and post-doctoral advisor (if relevant) are conflicts for life.

Collaboration: You have a collaboration on a project, publication, grant proposal, or editorship within the past two years.

Close friends and family: Close family relations (e.g., spouse, parent/child, sibling) and close friends are conflicts forever, if they are potential reviewers.

The PC will review paper conflicts to ensure the integrity of the reviewing process, adding conflicts if necessary. If there is no basis for conflicts indicated by authors, such conflicts will be removed. Do not identify PC members as a conflict solely to avoid having them as reviewers. If you have any questions about conflicts, contact the program co-chairs.

Author Notification and Beyond

Authors will be notified of paper acceptance or rejection according to the schedule above. If your paper is accepted and you need an invitation letter to apply for a visa to attend the conference, contact as soon as possible. Visa applications can take at least 30 working days to process. Identify yourself as a presenter and include your mailing address in your email.

Early Rejection Notification. This year, we will notify authors of papers that are rejected early in the process, prior to the author response period. The goal is to allow authors of early rejected papers to use reviewer feedback earlier and resubmit to another conference as soon as possible. Early rejected papers will no longer be considered under submission (regarding multiple submission policies) upon receipt of a rejection notification.

All papers will be available online to registered attendees no earlier than Tuesday, January 30, 2024. If your accepted paper should not be published prior to the event, please notify The papers will be available online to everyone beginning on the first day of the main conference, Tuesday, February 27, 2024. Accepted submissions will be treated as confidential prior to publication on the USENIX FAST '24 website; rejected submissions will be permanently treated as confidential.

By submitting a paper, you agree that at least one of the authors will attend the conference to present it. If the conference registration fee will pose a hardship for the presenter of the accepted paper, please contact