G Appendix – RPASCE Performance TuningTips
This appendix includes tips and information to help you configure the RPASCE application so that it is as efficient as possible. RPASCE provides various configuration controls for fine tuning the execution. For example, for batch rule groups and rule groups that run in system workbook such as Java special expression rule groups, you can add certain rule group properties to achieve better performance. A configurator understands measure data volume and patterns and can choose from the following tips appropriately to apply to their configuration.
Rule Group Properties
This section provides information about rule group properties.
swaphierorder
Background:
In general, the hierarchy is ordered as clnd/prod/loc. However, for certain special expressions that run in the system workbook, the iteration pattern is, for each PROD,to iterate all LOC positions and cause long run time. To run such an expression efficiently, the hierarchy order must be temporarily modified within the system workbook to use CLND/LOC/PROD instead.
Configuration:
Add a rule group property swaphierorder=prod:loc for this batch rule group
Description:
For the rule group with this property set, when being evaluated in the system workbook, the system workbook will swap the ordering of the two hierarchies within the workbook itself. Consider, for example, if in the PDS, the hierarchy order for prod is 1000, the hierarchy order for loc is 1010, and the rule group A has this property set to prod:loc. Then, when rule group A is evaluated in the system workbook, the order for prod will be 1010 and the order for loc will be 1000. This will cause the arrays within the system workbook to be created with a different dim space in order to optimize the array operations for this rule group A.
Note that this property does not change the hierarchy order within the PDS. This property can also be dynamically set using Tools APIs during the application’s plugin automation.
prerange
Background:
The system workbook for a rule group is built with the complete scope of the PDS. When the calculation in the rule group is restricted to a smaller scope, the configurator can use the mask measure to reduce the scope of the workbook to two levels:
At the partition level, if some partitions are masked off, it can reduce the number of partitions. Within the system workbook, the scope of the dimension can be further reduced by the positions identified by the mask measures, if the mask measure’s base intersection is lower than the partition level, which in most cases is true. With this approach, we can reduce the number of system workbooks to build and reduce the scope within the system workbook.
Rule Group Property Configuration:
Add the rule group property prerange for this batch rule group.
The property prerange must be set in the format of “hierName:measName,hierName:measName...”. For example, "prod:skuMask1,loc:strMask2..."
Description:
If set, and if the rule group is evaluated in a system workbook, the hierarchies in the system workbook will be ranged using the mask measure specified for each hierarchy.
This property can also be dynamically set using Tools APIs during the application’s plugin automation.
purgeflag
Background:
A flag is required to tell RPASCE, for the ranged rule group using “prerange” flag, RPASCE must purge the older data before calculation. When this purgeflag property is not set, RPASCE treat it as “false” (that is, do not purge).
Rule Group Property Configuration:
Add a rule group property purgeflag=true for this batch rule group.
Description:
If set to true, if the rule group is evaluated in a system workbook, then before the system workbook is built, the LHS tables referenced in the rule group will be purged and all rows will be deleted.
This property can also be dynamically set using Tools APIs during the application’s plugin automation.