QVS Event Log is generating the warning messages:System: when AAALR(8.340125) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency.
System: - aggregating on 'IDEA_TARGET_FACT'(%KEY_EXEC_GROUP) with Cardinal(164), for Object: Document\CH431_309715473 in Doc:Environment:
Large, resource-intensive application required a different algorithm in the calculation engine.
"AAALR" is a very low level concept deep in the engine. Generally speaking it means the average length of aggregation array. The longer this array is, the more memory and CPU power are to be used by the engine to get aggregation result for every hypercube node.
When AAALR is greater than 1.0, normally the customer has a large data set and suffers slow responses and high memory usage in their app. In this case, a setting called “DisableNewRowApplicator” can be applied in the settings.ini (C:/Programdata/QlikTech/QlikViewServer) for QlikView Server.
By setting this parameter to “0”, QlikView will use a new algorithm which is optimized for large data set to do the aggregation, and will use much less memory and CPU power.
If there is no noticeable performance issue despite this message is output, this warning can also just simply be ignored. “SELOG_AAALR=0” can be set in the settings.ini to disable the warning message.
Alternatively, “AAALRGate_” can be set to any value to change the threshold of dumping this warning message. For example, if “AAALRGate_=1100.0” is set, no warning will be output any more until an object's AAALR reaches 1100 or more.
- If the customer has an app which contains large data set and is suffering from bad performance (high memory usage and poor response time), and this warning is output in the logs, they should try “DisableNewRowApplicator=0” to see if it solves their problem.
DisableNewRowApplicator=1: use Engine default.
DisableNewRowApplicator=0: use new row applicator where Engine reckons suitable.
DisableNewRowApplicator=-1: force to use new row applicator all the time. (Only available in 11.20 SR16 and higher)
- If there is no noticeable performance issue, just simply set “SELOG_AAALR=0” to disable the warning or “AAALRGate_=1100.0” to set a higher threshold. Please note that when enabling the NewRowApplicator QlikView Server service will create a new index in memory for each calculation in order to accelerate calculation speed and that may result in a slight increased memory and CPU usage. This warning shall be viewed as an indication that there could be benefits in enabling the New Row Applicator feature, however as the impact will be different depending on the environment, customer should be careful and monitor if the environment performs better or worse after the setting has been enabled.Note:
In a multi-nodes environment, the settings should be added in the settings.ini file for each of the node holding the QlikView Server service.
The setting needs to be applied in the settings.ini file in as a [Settings 7] property. Example: