28 Jan
2011
28 Jan
'11
11:56 a.m.
On 24 jan 2011, at 23:47, Norbert Hartl wrote:
It is hard to tell. Usually you can assume that an
OODB is more partitioned (data wise) than a relational database. This leads to more seeks
on a hard drive.
Not when using an OO model and following the navigation. Objects that are created together
are close together. A simple example: An order has orderlines. In an OODB you would expect
the orderlines to be on the same (or next) page on disk. With a RDBMS, you need to access
two tables, and have two seeks. A full table scan over orders though is of course slower
with an OODB, as more pages need to be loaded.
Stephan