HydraFS: an efficient NUMA-aware in-memory file system

Ting Wu, Xianzhang Chen, Kai Liu*, Chunhua Xiao, Zhixiang Liu, Qingfeng Zhuge, Edwin H.M. Sha

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

3 Scopus citations

Abstract

Emerging persistent file systems are designed to achieve high-performance data processing by effectively exploiting the advanced features of Non-volatile Memory (NVM). Non-uniform memory access (NUMA) architectures are universally used in high-performance computing and data centers due to its scalability. However, existing NVM-based in-memory file systems are all designed for uniformed memory access systems. Their performance is not satisfactory on NUMA machine as they do not consider the architecture of multiple nodes and the asymmetric memory access speed. In this paper, we design an efficient NUMA-aware in-memory file system which distributes file data on all nodes to effectively balance the loads of file requests. Three approaches for improving the performance of the file system on NUMA machine are proposed, including Node-oriented File Creation algorithm to dispatch files over multiple nodes, File-oriented Thread Binding algorithm to bind threads to the gainful nodes and a buffer assignment technique to allocate the user buffer from the proper node. Further, based on the new design, we implement a functional NUMA-aware in-memory file system, HydraFS, in Linux kernel. Extensive experiments show that HydraFS significantly outperforms existing representative in-memory file systems on NUMA machine. The average performance of HydraFS is 76.6%, 91.9%, 26.7% higher than EXT4-DAX, PMFS, and SIMFS, respectively.

Original languageEnglish
Pages (from-to)705-724
Number of pages20
JournalCluster Computing
Volume23
Issue number2
DOIs
StatePublished - 1 Jun 2020

Keywords

  • High performance
  • In-memory file systems
  • Load balancing
  • Multi-threads
  • NUMA

Fingerprint

Dive into the research topics of 'HydraFS: an efficient NUMA-aware in-memory file system'. Together they form a unique fingerprint.

Cite this