Design and evaluation of the mechanism for object references in a parallel object-oriented database system

Kenji Imasaki, Tsuyoshi Ono, Takaaki Horibuchi, Akifumi Makinouchi, Hirofumi Amano

Research output: Contribution to conferencePaper

1 Citation (Scopus)

Abstract

Four object reference mechanisms for a parallel Object-Oriented Database System (OODBS) and used by MAssively Parallel Programming LanguagE (MAPPLE) are tested by the parallel OO1 Benchmark. Out of these mechanisms, mechanisms using an Object Allocation Table (OAT) were the most successful when many objects existed and were moved across processors. The OAT stores Object IDentifiers(OIDs) that are independent of the object location and are paired with an indicator of the object location. In addition, the evaluation results show that when the number of object references among processors is large, an OAT entry should be inserted when an object is created. If the number is small, an OAT entry should be inserted when an object is referenced for the first time.

Original languageEnglish
Pages337-346
Number of pages10
Publication statusPublished - Dec 1 1997
EventProceedings of the 1997 International Database Engineering & Applications Symposium - Montreal, Can
Duration: Aug 25 1997Aug 27 1997

Other

OtherProceedings of the 1997 International Database Engineering & Applications Symposium
CityMontreal, Can
Period8/25/978/27/97

Fingerprint

Parallel programming
Computer programming languages
Object-oriented databases

All Science Journal Classification (ASJC) codes

  • Computer Science(all)
  • Engineering(all)

Cite this

Imasaki, K., Ono, T., Horibuchi, T., Makinouchi, A., & Amano, H. (1997). Design and evaluation of the mechanism for object references in a parallel object-oriented database system. 337-346. Paper presented at Proceedings of the 1997 International Database Engineering & Applications Symposium, Montreal, Can, .

Design and evaluation of the mechanism for object references in a parallel object-oriented database system. / Imasaki, Kenji; Ono, Tsuyoshi; Horibuchi, Takaaki; Makinouchi, Akifumi; Amano, Hirofumi.

1997. 337-346 Paper presented at Proceedings of the 1997 International Database Engineering & Applications Symposium, Montreal, Can, .

Research output: Contribution to conferencePaper

Imasaki, K, Ono, T, Horibuchi, T, Makinouchi, A & Amano, H 1997, 'Design and evaluation of the mechanism for object references in a parallel object-oriented database system', Paper presented at Proceedings of the 1997 International Database Engineering & Applications Symposium, Montreal, Can, 8/25/97 - 8/27/97 pp. 337-346.
Imasaki K, Ono T, Horibuchi T, Makinouchi A, Amano H. Design and evaluation of the mechanism for object references in a parallel object-oriented database system. 1997. Paper presented at Proceedings of the 1997 International Database Engineering & Applications Symposium, Montreal, Can, .
Imasaki, Kenji ; Ono, Tsuyoshi ; Horibuchi, Takaaki ; Makinouchi, Akifumi ; Amano, Hirofumi. / Design and evaluation of the mechanism for object references in a parallel object-oriented database system. Paper presented at Proceedings of the 1997 International Database Engineering & Applications Symposium, Montreal, Can, .10 p.
@conference{a14f82e1b30549beab1b2c6ecbf7d0f8,
title = "Design and evaluation of the mechanism for object references in a parallel object-oriented database system",
abstract = "Four object reference mechanisms for a parallel Object-Oriented Database System (OODBS) and used by MAssively Parallel Programming LanguagE (MAPPLE) are tested by the parallel OO1 Benchmark. Out of these mechanisms, mechanisms using an Object Allocation Table (OAT) were the most successful when many objects existed and were moved across processors. The OAT stores Object IDentifiers(OIDs) that are independent of the object location and are paired with an indicator of the object location. In addition, the evaluation results show that when the number of object references among processors is large, an OAT entry should be inserted when an object is created. If the number is small, an OAT entry should be inserted when an object is referenced for the first time.",
author = "Kenji Imasaki and Tsuyoshi Ono and Takaaki Horibuchi and Akifumi Makinouchi and Hirofumi Amano",
year = "1997",
month = "12",
day = "1",
language = "English",
pages = "337--346",
note = "Proceedings of the 1997 International Database Engineering & Applications Symposium ; Conference date: 25-08-1997 Through 27-08-1997",

}

TY - CONF

T1 - Design and evaluation of the mechanism for object references in a parallel object-oriented database system

AU - Imasaki, Kenji

AU - Ono, Tsuyoshi

AU - Horibuchi, Takaaki

AU - Makinouchi, Akifumi

AU - Amano, Hirofumi

PY - 1997/12/1

Y1 - 1997/12/1

N2 - Four object reference mechanisms for a parallel Object-Oriented Database System (OODBS) and used by MAssively Parallel Programming LanguagE (MAPPLE) are tested by the parallel OO1 Benchmark. Out of these mechanisms, mechanisms using an Object Allocation Table (OAT) were the most successful when many objects existed and were moved across processors. The OAT stores Object IDentifiers(OIDs) that are independent of the object location and are paired with an indicator of the object location. In addition, the evaluation results show that when the number of object references among processors is large, an OAT entry should be inserted when an object is created. If the number is small, an OAT entry should be inserted when an object is referenced for the first time.

AB - Four object reference mechanisms for a parallel Object-Oriented Database System (OODBS) and used by MAssively Parallel Programming LanguagE (MAPPLE) are tested by the parallel OO1 Benchmark. Out of these mechanisms, mechanisms using an Object Allocation Table (OAT) were the most successful when many objects existed and were moved across processors. The OAT stores Object IDentifiers(OIDs) that are independent of the object location and are paired with an indicator of the object location. In addition, the evaluation results show that when the number of object references among processors is large, an OAT entry should be inserted when an object is created. If the number is small, an OAT entry should be inserted when an object is referenced for the first time.

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

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

M3 - Paper

AN - SCOPUS:0031360205

SP - 337

EP - 346

ER -