• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations | Disambiguate

DMCA

Journaling of Journal Is (Almost) Free

Cached

  • Download as a PDF

Download Links

  • [www.cs.rochester.edu]
  • [ftp.cs.rochester.edu]
  • [www.cs.rochester.edu]
  • [www.cs.rochester.edu]
  • [www.cs.rochester.edu]
  • [www.cs.rochester.edu]
  • [ftp.cs.rochester.edu]
  • [ftp.cs.rochester.edu]
  • [www.cs.rochester.edu]

  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Kai Shen , Stan Park , Meng Zhu
Citations:3 - 0 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@MISC{Shen_journalingof,
    author = {Kai Shen and Stan Park and Meng Zhu},
    title = {Journaling of Journal Is (Almost) Free},
    year = {}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

Lightweight databases and key-value stores manage the consistency and reliability of their own data, often through rollback-recovery journaling or write-ahead logging. They further rely on file system journaling to protect the file system structure and metadata. Such journaling of journal appears to violate the classic end-to-end argument for optimal database design. In practice, we observe a significant cost (up to 73 % slowdown) by adding the Ext4 file system journaling to the SQLite database on a Google Nexus 7 tablet running a Ubuntu Linux installation. The cost of file system journaling is up to 58 % on a conventional machine with an Intel 311 SSD. In this paper, we argue that such cost is largely due to implementation limitations of the existing system. We apply two simple techniques—ensuring a single I/O operation on the synchronous commit path, and adaptively allowing each file to have a custom journaling mode (in particular, whether to journal the file data in addition to the metadata). Compared to SQLite without file system journaling, our enhanced journaling improves the performance or incurs minor (<6%) slowdown on all but one of our 24 test cases (with 14 % slowdown in the exceptional case). On average, our enhanced journaling implementation improves the SQLite performance by 7%. 1

Keyphrases

file system journaling    classic end-to-end argument    key-value store    optimal database design    synchronous commit path    enhanced journaling    file data    rollback-recovery journaling    ubuntu linux installation    google nexus    file system structure    sqlite performance    file system    conventional machine    sqlite database    ext4 file system    enhanced journaling implementation    exceptional case    implementation limitation    significant cost    lightweight database    simple technique    test case    custom journaling mode    write-ahead logging   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University