Optimizing rule calcs with tm1s.cfg parameters?

[jonathan.d]

Hi All,

Need some advice/info before considering to use 'AllRuleCalcStargateOptimization' and 'ViewConsolidationOptimizationMethod ' .

Does anybody have more info on these two setting other than what's in the help files?.

Also,

AllRuleCalcStargateOptimization - Is there a significant performance increase when enabled?

ViewConsolidationOptimizationMethod - If a TREE method is recommended, why is the default set to Array?


Below I have copy pasted the info in the help file regarding these two parameters for quicker reference.

Appreciate any help/advice in regards to these two parameters as well as speeding up rule calculations in general.



AllRuleCalcStargateOptimization

The AllRuleCalcStargateOptimization parameter can improve performance in calculating views that contain only rule-calculated values.
Typically, TM1 performs calculations for standard consolidations and then calculates values for rule-based consolidations, which may end up overriding values in the standard consolidations. The AllRuleCalcStargateOptimization parameter provides optimization that first checks if every value in the view is rule-calculated and then proceeds as follows:
• If every value in the view is rule-calculated, then TM1 skips the unnecessary calculations for standard consolidations and just performs the rule-calculated consolidations.
• If the view contains even a single value which is not rule-calculated, then this optimization parameter will have no effect. (Does this mean it works in default mode?)
When this parameter is set to True, some additional processing will take place for every view that is requested to first check if the view contains only rule-calculated values. For most views, this additional processing is minimal since the optimization is stopped after the first value in the view is found to be not rule-calculated.
To enable this parameter, set the parameter’s value to T in the TM1 server configuration file, Tm1s.cfg, as follows:
AllRuleCalcStargateOptimization=T
The default setting is disabled (F).

ViewConsolidationOptimizationMethod
This parameter defines the method used to achieve view consolidation optimization when the ViewConsolidationOptimization parameter is enabled on the TM1 server.
There are two methods that ViewConsolidationOptimization can use to calculate and store consolidations: ARRAY or TREE. The ARRAY method stores consolidations in a temporary array. The TREE method stores consolidations in a tree.
ViewConsolidationOptimizationMethod should be set to TREE in most circumstances. This setting provides the best performance in normal operations and when data is sparse along the view axes.
In the uncommon circumstance when axes dimensions have just a few leaf elements rolling up to many consolidations, ViewConsolidationOptimizationMethod should be set to ARRAY.
To set this parameter, add the appropriate line to your configuration file:
ViewConsolidationOptimizationMethod=TREE
ViewConsolidationOptimizationMethod=ARRAY
If ViewConsolidationOptimizationMethod is not explicitly set in the Tm1s.cfg file, the ARRAY method is used by default.

[lotsaram]

Is AllRuleCalcStargateOptimization new with 9.4 or 9.5? I haven't come across it before ... just looked it up in the 9.5 operations guide though and it is listed.

As to whether it is effective in improving performance I guess that would depend on how many large or otherwise calculation intensive rule only views were being queried as the performance gain is only going to apply to those specific cases.