Priming the System with Demand-Defined Aggregates

The AtScale engine can generate demand-defined aggregates before analysts start querying your data, which may improve the performance of the initial queries they issue. Priming is done by enabling Training Mode on the Settings page, then running queries representative of the queries that analysts will issue.

When you deploy a model, the AtScale engine defines and builds instances of all-member and dimension-only aggregates (see Types of Aggregate Tables in AtScale). However, the engine creates demand-defined aggregates only as queries are issued against the model. This means that queries the engine has not yet seen, that do not resemble other initial queries on the model, or that cannot be satisfied by prediction-defined aggregates will run against raw data. As the engine builds, maintains, and revises a repertoire of aggregate tables, queries start running against the aggregate tables rather than the raw data, and query performance starts to improve.

If you know the types of queries analysts will use, you can run similar ones in Training Mode so the engine generates demand-defined aggregates. Training Mode runs queries, but does not return results.

To prime AtScale with demand-defined aggregates:

1. Deploy a catalog.

2. Go to the Settings page > User Settings tab.

3. Under Enable Training Mode, set the duration you want to enable Training Mode for, then click Enable.

   Note

   When Traning Mode is enabled, queries issued from BI tools (from any user) will not return any data.

4. Issue queries from your data-analytics software.

5. Return to the User Settings tab in Design Center and click Cancel to disable Training Mode.

You can then let analysts know that they can begin querying the models.

For more information on Traning Mode, see Settings Page.