ACM Home Page
Please provide us with feedback. Feedback
Optimal policy for batch operations: backup, checkpointing, reorganization, and updating
Full text PdfPdf (77 KB)
Source International Conference on Management of Data archive
Proceedings of the 1977 ACM SIGMOD international conference on Management of data table of contents
Toronto, Ontario, Canada
SESSION: Data base integrity and protection table of contents
Pages: 157 - 157  
Year of Publication: 1977
Authors
Guy M. Lohman  California Institute of Technology
John A. Muckstadt  Cornell University
Sponsor
SIGMOD: ACM Special Interest Group on Management of Data
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 21,   Citation Count: 0
Additional Information:

abstract   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/509404.509429
What is a DOI?

ABSTRACT

Many database maintenance operations are performed periodically in batches, even in real-time systems. The purpose of this paper is to present a general model for determining the optimal frequency of these batch operations. Specifically, optimal backup, checkpointing, batch updating, and reorganization policies are derived. The approach used exploits inventory parallels, by seeking the optimal number of items --- rather than a time interval --- to trigger a batch. The Renewal Reward Theorem is used to find the average long run costs for backup, recovery, and item storage, per unit time, which is then minimized to find the optimal backup policy. This approach permits far less restrictive assumptions about the update arrival process than did previous models, as well as inclusion of storage costs for the updates. The optimal checkpointing, batch updating, and reorganization policies are shown to be special cases of this optimal backup policy. The derivation of previous results as special cases of this model, and an example, demonstrate the generality of the methodology developed.


Collaborative Colleagues:
Guy M. Lohman: colleagues
John A. Muckstadt: colleagues