Performance Tuning

By - Updated June 3, 2019

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 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.

Notification Table: For Rolap storage mode, you can specify a table within the application database from which to listen for data changes. Any changes detected in that table will cause this partition to automatically refresh.

Partition Mode: The partition mode can be specified if model uses a Time dimension. The partition model 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.


Selecting the right size for dimension when design.

Make clear definition and proper prediction for dimension and choose a suitable size for it.

Please note: The size cannot be changed once set.

Do not turn on Hierarchy property and Security of dimension attribute when not necessary


Security option will allow administrators to grant users access in the dimension member level. For instance, When Entity dimension’s Security is turned on, you can specify that User A only has access to United States and Canada data. For more information, please refer to Dimensional Member Security Access section in Kepion Planning Administrator Guide.


Scope context and selection context can be sent to as part of the parameters (@Scope, @SelectionScope) for the rule execution.

For performance consideration, Exclude form scope context and Exclude form selection context should be uncheck.

For more details of these two parameters, please refer to the SQL Rule section in Kepion Planning Modeler Guide.


Default each member to the lowest member within a hierarchy to give better performance when the form is first opened.