Abstract
Due to the volatility of main memory, a Memory Database (MMDB) system may lose the primary copy of its database after a system failure. The lost database can be recovered by reloading the archive database residing on Archive Memory (AM) into Main Memory (MM) and applying log data. This paper analyzes three major issues that directly impact the reload performance: how to organize the database on AM, how to choose the reload granularity, and how to create address translation tables. The paper proposes an AM structure which makes use of disk striping to reduce reload time, and a special AM structure on which data blocks are organized based on their access frequency order to ensure hot spots are reloaded before less frequently used data. Our analysis shows that cylinder is the best reload granularity in terms of total reload time and transaction waiting time.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
