Compression Tests


The following tests estimate the amount of disk space required to store the same dataset containing 10+ million time:value samples in different databases.


Database Version Schema Compressed Bytes per Sample Test Link
ATSD 17340 Universal Yes 1.9 view
Microsoft SQL Server 14.0.1000.169 Specific Yes 9.4 view
Microsoft SQL Server 14.0.1000.169 Specific No 19.3 view
Microsoft SQL Server 14.0.1000.169 Universal Yes 42.9 view
Microsoft SQL Server 14.0.1000.169 Universal No 89.5 view
MySQL 5.7 Specific Yes 8.2 view
MySQL 5.7 Specific No 15.6 view
MySQL 5.7 Universal Yes 34.5 view
MySQL 5.7 Universal No 70.7 view
Oracle Specific Yes 9.4 view
Oracle Specific No 13.4 view
Oracle Universal Yes 39.3 view
Oracle Universal No 52.5 view
PostgreSQL 9.6 Specific No 21.6 view
PostgreSQL 9.6 Universal No 83.7 view
Vertica 7.1.1-0 Specific Yes 2.4 view
Vertica 7.1.1-0 Universal Yes 5.6 view


The dataset represents 20+ years of historical minutely stock trade data available from the Kibot company.

Minutely trade statistics are available for IBM stock traded on the New York Stock Exchange. Recording begins on February 1st, 1998 and continues until the most recent trading day.

The data is provided in the commonly used OHLCV format.


The records be downloaded from the following url:

The file contains over 2 million lines. The OHLC metrics contain values with up to four decimal places. The volume metric is an integer. The dates are recorded in US/Eastern time.

Each row consists of 5 metrics for a given 1-minute interval:

time   = 09/08/2017 15:42
open   = 142.53
high   = 142.5399
low    = 142.49
close  = 142.49
volume = 10031

Schema Alternatives

The tests are performed using two schema options:

Specific Table

The Specific Table schema uses a named column for each metric.

Under this option, the table is configured to store a fixed set of metrics for the given entity type. A separate table is required for each type of entity.

Example: IBM Tivoli Data Warehouse


Universal Table

The Universal Table schema uses a Metric Id column to reference the metric defined in a separate dictionary (lookup) table.

This option allows adding new metrics without altering the data table itself.

Example: Microsoft System Center Operations Manager Data Warehouse