Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Datamarts Size factors

The Datamarts stores store information from different data sources. During the loading process, O3 performs a set of optimizations and transformations, which have several consequences:

  • The information is highly compressed because they are compact representations of information (compared with relational databases, files, etc..)
  • Aggregations As aggregations are performed, the information in the DataMart does not have the same detail as in the sources, so for each record actually stored in a the DataMart, O3 may have loaded several records of the sources. This factor also contributes to the compression of information.
  • To improve the query, some Datamarts are designed to perform a set of Pre-Calculus (controlled redundancy), which increases the information stored in the DataMart.
  • Only a portion of the information in the databases that act of information sources for the Analysis is acatuallly is actuallly used by Datamarts.

As general rule, the Datamarts show rates of compression of the information they store, requiring less storage space that than the databases that originate the information.

Datamarts Size

Ejemplo Example

Registros efectivos en el Datamart Effective Records

Tamaño sin Size without Pre-Cálculo Tamaño después de Calculus

Size after Pre-Cálculo Calculus

APB S

7 millones millons

350 MB

560 MB

APB L

18.8 millones millons

870 MB

1.25 GB

APB XL

94.5 millones millons

4.45 GB

6.5 GB