You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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?
The text was updated successfully, but these errors were encountered: