During the application build process, there are several performance tuning options available to consider. There are four main areas for performance tuning with Kepion: Data Partition, Dimension Sizing, SQL Rules, and Form Build.
When performance tuning a partition, you must first determine its storage mode. The storage mode controls how data is stored in the cube when the application is deployed to OLAP. It is suggested to change the Storage Mode to MOLAP for a static non-Writeback partition.
You can also configure a partition with the following performance tuning properties:
Rolap Slice: For Rolap storage mode, you can configure the OLAP slice property of a partition to indicate the type of data stored in this partition. Setting this property can boost OLAP query performance.
Partition Mode: The Partition Mode can be specified if model uses a Time Dimension. The Partition Mode can be set to the following properties:
- By Months: Auto generate additional partitions in OLAP with the data segmented by months
- By Years: Auto generate additional partitions on OLAP with the data segmented by years
Partition Interval: This setting determines the time interval between each generated partition as specified in the Partition Mode.
Through configuring the above settings, Kepion will generate SSAS partitions automatically from your single partition into multiple partitions, and split the data by the specified groups. Kepion will also use the Time Dimension defined on the Model to determine the start and end range for the time.
This technique can help boost processing time for very large partitions. However, please ensure that the partition is set to MOLAP, as this technique is not helpful for ROLAP partitions. The partition in SQL will not be affected. This feature will only generate additional partitions in SSAS with the Time filter for each range of data.
Selecting the right size for the Dimension when designing.
Make a clear definition and proper prediction for the Dimension and choose a suitable size for it. Do not turn on Security or All Hierarchy Dimension attributes when not necessary.
The Security option will allow administrators to grant users access in the Dimension Member level. For instance, when the Department Dimension’s Security is turned on, you can specify a user to only have access to Finance and Marketing data.
Scope context and selection context can be sent to as part of the parameters (@Scope, @SelectionScope) for the rule execution.
For performance consideration, Include form scope and Include form selection should be unchecked.
You should always default each member to the lowest member within a hierarchy to give better performance when a Form is first opened.