Free Transactions with Rio Vista

Free Transactions with Rio Vista - F ree Transactions with...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Free Transactions with Rio Vista This paper talks about transactions and recovery in virtual memories for the purpose of making data persistent. This paper mainly revolves around a system called Rio-Vista and is a comparative study with a similar and older technology called the LRVM. The paper begins with an introduction about persistence and transactions. Transactions are used often in software systems for the purpose of persistence of data. Its a commonly used terminology in databases. Making a virtual memory persistent means allowing atomic updates and persistence of the virtual memory. But the problem with traditional transaction management techniques when they have to be implemented as a system program or a kernel program it that it is not a light weight program. Usually committing a transaction requires at least one I/O access which by itself is several milliseconds long. So normally system programmers traditionally avoided bringing in transaction processing with kernels. This paper is an attempt to reduce the inefficiencies and complexity associated with a transaction mgmt system and provide a good alternative. It achieves a performance gain of the order of 2000 times the normal systems. It is achieved through the two components in the systems namely Rio and Vista. The Rio file cache is a persistent area in main memory that is assisted with an uninterruptible power supply. Its a persistent file cache. Vista is a transaction mgmt library which runs on top of rio. This library was achieved as a 720 lines of code library that involves all the necessary functionality associated with the API .The library alone achieves a 100 fold improvement over other system when we run them on rio. The paper then gives a brief description of how an earlier system RVM works. In RVM an Undo-Redo log system is used. At the beginning of a transaction, the memory about to be modified is copied in to an undo log and the operations are performed. At the end of the transaction or during a commit, the data is written to a redo log which essentially contains
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
a set of committed records. At some point of time all the records are written to the data base store on the disc. If a program aborts or fails unexpectedly, the VM can be made
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 05/20/2010 for the course EFR 3456 taught by Professor Poo during the Spring '10 term at Manhattan College.

Page1 / 5

Free Transactions with Rio Vista - F ree Transactions with...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online