Object Oriented Database Learning Center

Objectivity Home - Government - Objectivity/DB - Webinars - Download Software

Download a PDF version of this Article

Table of contents:

Object Oriented Database vs Relational Database

• Introduction
• The Wall: Where an RDBMS breaks down
• Programming Time and Cost
• Integrity Loss
• Performance
• Information Model Issues
• Architecture Issues
• Benchmark
• Benchmark Parameters
• Benchmark Execution
• Parts Creation
• Updates
• Deletes
• Selects
• Summary
• Examples
• Cimskil (Manufacturing)
• Exxon (Configuration and FEA)
• CERN (Data Gathering and Analysis)
• Decision•ism (Decision Supportware)
• QUALCOMM (Telecommunications)
• COM21 (Cable Modem)
• Nortel, Sprint (Cell Phone Base Station Management)
• Nousoft (Library Document Management, Web)
• Iridium (Telecommunications)
• BBN (Military Logistics and Control)
• Intraspect (Knowledge Management)
• Fisher-Rosemount (Manufacturing, Process Control)
• A Brief Overview of Our Development
• ODB Selection
• Introduction
• Performance
• Scalability
• Productivity
• Fault Tolerance
• Additional Features and Benefits
• Summary
• Kintetsu (Transportation, Logistics)
• Siemens (Process Control)
• SEH (Semiconductor Manufacturing)
• NEC (Semiconductor Manufacturing)
• American Meter (Process Control)
• Sloan Digital Sky Survey (Geographic Information System)
• LMS (Healthcare, Fetal Monitoring)
• Synthesis (Healthcare, Record Management)
• Daikin (Multi-Media CD-I Authoring)
• How to Avoid the Wall

Object Oriented Database vs Relational Database

Selects

The last benchmark run was the select phase. In this phase a separate program was run that scanned all Part trees and printed out each record. The total time to connect to the database and print each record was then recorded. Note that the records were printed to a file, so screen I/O would not play a part in the results. Here are the results of those runs (times in ms).

Objectivity is twice as fast as the RDBMS for a very small amount of records and "blows the RDBMS" off the scale for a large amount of records. Objectivity was able to print 1800 records per second in the last test, while the RDBMS averaged about 200 per second in all runs.

This clearly shows the exponential superiority of Objectivity/DB over the leading RDBMS in typical network or hierarchy applications. One might wonder what is sacrificed for this advantage — perhaps SQL is slower or less functional, or ODBC tools are slower or less functional. To investigate this, we continue the benchmark to compare SQL and ODBC behavior. The results show that not only is there no loss in performance or functionality, but, as the complexity increases, the Objectivity/SQL++ query optimizer performs increasingly better than the RDBMS one, because it is able to optimize based on the objects and relationships in the database.