jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clay Ferguson <wcl...@gmail.com>
Subject Re: Node Retrieval Performance
Date Sat, 14 Nov 2015 18:37:38 GMT
Sorry Ron,
You have it precisely backwards. In RDBMS modeling you focus on the
organization of the data and relationships of the data, and never break
stuff up to "help" the DB loading. For example, once you see the need for a
PERSONS table, you generally have just *one* PERSONS table even if you have
millions of people. In an RDBMS you never find yourself searching for
patterns in the data just so you can break stuff up to help provide a
crutch for the DB engine. DB indexes are all that are required to solve
scalability. NEVER breaking up data.

On Sat, Nov 14, 2015 at 11:43 AM, Ron Wheeler <
rwheeler@artifact-software.com> wrote:

> Even in an RDBMS application, the database designer has to be aware of the
> physical structure used by the implementation if you want to have
> reasonable performance with large numbers of records.
> You have to do tuning and give some thought to the way you structure your
> tables and indexes.
> That may mean splitting tables in ways that have little to do with the
> business logic in order to get the best performance in the most common or
> critical cases.
> That is why we have database administrators and courses at the university
> level on data structures.
> Ron

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message