Object Fault Handling for Persistent Programming Languages: A Performance Evaluation

Antony L. Hosking; J. Eliot B. Moss

doi:10.1145/167962.165907

Object Fault Handling for Persistent Programming Languages: A Performance Evaluation

Antony L. Hosking, J. Eliot B. Moss

Research output: Contribution to journal › Article › peer-review

18 Citations (Scopus)

Abstract

key mechanism of a persistent programming language is its ability to detect and handle references to non-resident objects. Ideally, this mechanism should be hidden from the programmer, allowing the transparent manipulation of all data regardless of its potential lifetime. We term such a mechanism object faulting, in a deliberate analogy with page faulting in virtual memory systems. This paper presents a number of mechanisms for detecting and handling references to persistent objects, and evaluates their relative performance within an implementation of Persistent Smalltalk.

Original language	English
Pages (from-to)	288-303
Number of pages	16
Journal	ACM SIGPLAN Notices
Volume	28
Issue number	10
DOIs	https://doi.org/10.1145/167962.165907
Publication status	Published - 10 Jan 1993
Externally published	Yes

Access to Document

10.1145/167962.165907

Cite this

@article{530608004f334d3e907d9cc458276796,

title = "Object Fault Handling for Persistent Programming Languages: A Performance Evaluation",

abstract = "key mechanism of a persistent programming language is its ability to detect and handle references to non-resident objects. Ideally, this mechanism should be hidden from the programmer, allowing the transparent manipulation of all data regardless of its potential lifetime. We term such a mechanism object faulting, in a deliberate analogy with page faulting in virtual memory systems. This paper presents a number of mechanisms for detecting and handling references to persistent objects, and evaluates their relative performance within an implementation of Persistent Smalltalk.",

author = "Hosking, {Antony L.} and Moss, {J. Eliot B.}",

year = "1993",

month = jan,

day = "10",

doi = "10.1145/167962.165907",

language = "English",

volume = "28",

pages = "288--303",

journal = "ACM SIGPLAN Notices",

issn = "0362-1340",

publisher = "Association for Computing Machinery (ACM)",

number = "10",

}

TY - JOUR

T1 - Object Fault Handling for Persistent Programming Languages

T2 - A Performance Evaluation

AU - Hosking, Antony L.

AU - Moss, J. Eliot B.

PY - 1993/1/10

Y1 - 1993/1/10

N2 - key mechanism of a persistent programming language is its ability to detect and handle references to non-resident objects. Ideally, this mechanism should be hidden from the programmer, allowing the transparent manipulation of all data regardless of its potential lifetime. We term such a mechanism object faulting, in a deliberate analogy with page faulting in virtual memory systems. This paper presents a number of mechanisms for detecting and handling references to persistent objects, and evaluates their relative performance within an implementation of Persistent Smalltalk.

AB - key mechanism of a persistent programming language is its ability to detect and handle references to non-resident objects. Ideally, this mechanism should be hidden from the programmer, allowing the transparent manipulation of all data regardless of its potential lifetime. We term such a mechanism object faulting, in a deliberate analogy with page faulting in virtual memory systems. This paper presents a number of mechanisms for detecting and handling references to persistent objects, and evaluates their relative performance within an implementation of Persistent Smalltalk.

UR - http://www.scopus.com/inward/record.url?scp=84976834943&partnerID=8YFLogxK

U2 - 10.1145/167962.165907

DO - 10.1145/167962.165907

M3 - Article

AN - SCOPUS:84976834943

SN - 0362-1340

VL - 28

SP - 288

EP - 303

JO - ACM SIGPLAN Notices

JF - ACM SIGPLAN Notices

IS - 10

ER -

Object Fault Handling for Persistent Programming Languages: A Performance Evaluation

Abstract

Access to Document

Other files and links

Fingerprint

Cite this