Reducing the virtual memory overhead of swizzling

Authors:
V. Narasayya;T. S. E. Ng;D. McNamee;A. Tiwary;H. Levy
Affiliations:
-;-;-;-;-
Venue:
IWOOOS '96 Proceedings of the 5th International Workshop on Object Orientation in Operating Systems (IWOOOS '96)
Year:
1996

Citing 8
Cited 0

Pointer swizzling at page fault time: efficiently supporting huge address spaces on standard hardware

ACM SIGARCH Computer Architecture News
The ObjectStore database system

Communications of the ACM
Working with Persistent Objects: To Swizzle or Not to Swizzle

IEEE Transactions on Software Engineering
The 007 Benchmark

SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
QuickStore: a high performance mapped object store

SIGMOD '94 Proceedings of the 1994 ACM SIGMOD international conference on Management of data
Prototyping Bubba, A Highly Parallel Database System

IEEE Transactions on Knowledge and Data Engineering
A Performance Study of Alternative Object Faulting and Pointer Swizzling Strategies

VLDB '92 Proceedings of the 18th International Conference on Very Large Data Bases
Pointer swizzling techniques for object-oriented database systems

Pointer swizzling techniques for object-oriented database systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

Swizzling is a mechanism used by OODBs and persistent object systems to convert pointers from their disk format to a more efficient in-memory format. Previous studies of swizzling have focused on analyzing the CPU overhead of pointer translation and studying trade-offs in different approaches to swizzling. In this paper we show that there is an additional indirect but important cost associated with swizzling: swizzling a read-only page causes it to be "dirty" with respect to the operating system. At the onset of paging, these read-only pages may be written to the swap file unnecessarily. We propose a simple modification to the operating system that reduces the impact of this overhead on application performance.