Optimize mtt database for disk usage

[ompiteam]

The mtt database repeats many character strings thousands of times. For columns that contain such strings, a separate table should be created to index into from the main table. E.g., an entry that currently looks like:

||'''hostname''' ||'''test_name''' ||'''result''' ||
||somehost.com ||hello ||1 ||

Will instead look like:

||'''hostname''' ||'''test_name''' ||'''result''' ||
||index1 ||index2 ||1 ||

Where {{{hostname}}} and {{{test_name}}} tables exist that contain the following entries:

||'''index''' ||'''hostname''' ||
||index1 ||somehost.com ||
{{{}}}
||'''index''' ||'''test_name''' ||
||index2 ||hello ||

Will this significantly degrade performance?

[ompiteam]

Imported from trac issue 50. Created by emallove on 2006-08-31T10:17:13, last modified: 2006-12-15T11:23:06

[ompiteam]

Trac comment by emallove on 2006-09-02 09:49:57:

As Jeff pointed out to me, this will ''improve'' performance because instead of doing x number of string comparisons in our searches/aggregations, we will be doing x number of (speedier) integer comparisons.