File Download

There are no files associated with this item.

  • Find it @ UNIST can give you direct access to the published full text of this article. (UNISTARs only)
Related Researcher

백웅기

Baek, Woongki
Intelligent System Software Lab.
Read More

Views & Downloads

Detailed Information

Cited time in webofscience Cited time in scopus
Metadata Downloads

Full metadata record

DC Field Value Language
dc.citation.conferencePlace US -
dc.citation.conferencePlace Georgia TechAtlanta -
dc.citation.endPage 398 -
dc.citation.startPage 385 -
dc.citation.title Architectural Support for Programming Languages and Operating Systems -
dc.contributor.author Kim, Wook-Hee -
dc.contributor.author Kim, Jinwoong -
dc.contributor.author Baek, Woongki -
dc.contributor.author Nam, Beomseok -
dc.contributor.author Won, Youjip -
dc.date.accessioned 2023-12-19T21:07:31Z -
dc.date.available 2023-12-19T21:07:31Z -
dc.date.created 2016-07-06 -
dc.date.issued 2016-04-02 -
dc.description.abstract Emerging byte-addressable non-volatile memory is considered an alternative storage device for database logs that require persistency and high performance. In this work, we develop NVWAL (NVRAM Write-Ahead Logging) for SQLite. The proposed NVWAL is designed to exploit byteaddressable NVRAM to maintain the write-ahead log and to guarantee the failure atomicity and the durability of a database transaction. The contribution of NVWAL consists of three elements: (i) byte-granularity differential logging that effectively eliminates the excessive I/O overhead of filesystem-based logging or journaling, (ii) transactionaware lazy synchronization that reduces cache synchronization overhead by two-thirds, and (iii) user-level heap management of the NVRAM persistent WAL structure, which reduces the overhead of managing persistent objects. We implemented NVWAL in SQLite and measured the performance on a Nexus 5 smartphone and an NVRAM emulation board - Tuna. Our performance study shows the following: (i) the overhead of enforcing strict ordering of NVRAM writes can be reduced via NVRAM-aware transaction management. (ii) From the application performance point of view, the overhead of guaranteeing failure atomicity is negligible; the cache line flush overhead accounts for only 0.8∼4.6% of transaction execution time. Therefore, application performance is much less sensitive to the NVRAM performance than we expected. Decreasing the NVRAM latency by one-fifth (from 1942 nsec to 437 nsec), SQLite achieves a mere 4% performance gain (from 2517 ins/sec to 2621 ins/sec). (iii) Overall, when the write latency of NVRAM is 2 usec, NVWAL increases SQLite performance by at least 10x compared to that of WAL on flash memory (from 541 ins/sec to 5812 ins/sec). -
dc.identifier.bibliographicCitation Architectural Support for Programming Languages and Operating Systems, pp.385 - 398 -
dc.identifier.doi 10.1145/2872362.2872392 -
dc.identifier.scopusid 2-s2.0-84975311598 -
dc.identifier.uri https://scholarworks.unist.ac.kr/handle/201301/32806 -
dc.identifier.url http://dl.acm.org/citation.cfm?doid=2872362.2872392 -
dc.language 영어 -
dc.publisher Association for Computing Machinery -
dc.title NVWAL: Exploiting NVRAM in write-ahead logging -
dc.type Conference Paper -
dc.date.conferenceDate 2016-04-02 -

qrcode

Items in Repository are protected by copyright, with all rights reserved, unless otherwise indicated.