Adaptive logging for mobile device

Abstract

Nowadays, due to the increased user requirements of the fast and reliable data management operation for mobile applications, major device vendors use embedded DBMS for their mobile devices such as MP3 players, mobile phones, digital cameras and PDAs. However, database logging is the major bottleneck against the fast response time. There has been a lot of work minimizing logging overhead but no single recovery method provides the best performance to a variety of database workloads. In this paper, we present a novel recovery method called adaptive logging which can switch the logging method from ARIES to shadow paging adaptively at a page level according to the update state of each page on run time. Also, we propose a log compaction method called deferred logging which removes redundant logs by deferring to create log records until the updated data page is flushed or until the transaction commits. Deferred logging is coupled with adaptive logging seamlessly so that it boosts the performance of adaptive logging by reducing the typical overhead of hybrid methods. We have implemented the proposed approaches to our embedded DBMS which was deployed to more than 10 million mobile devices and evaluated them through a real world application on a mobile device. The result shows that our approaches can reduce logging overhead significantly and consequently can improve the response time of both small update transaction and large update transaction effectively.

MLC-flash-friendly logging and recovery for databases

“…In the past years, excellent ARIES-based recovery designs were proposed for different purposes, including those for multi-core and multi-socket hardware [8,9], large-scale distributed storage systems [12,20], and multi-thread and multi-server supports [4,6]. More recently, research has started exploring recovery for DBMSs over flash-memory storage systems, e.g., [1,11,13,14,18]. Excellent designs are such as a shadow-paging-based FlagCommit scheme to keep track of the transaction status for efficient transaction recovery in SLC-based DBMSs [18] and a transactional in-page logging (TIPL) approach to store updates into the specified log sector within a page for SLCbased databases [13].…”