Qlik Community

Ask a Question

Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
QlikWorld starts MONDAY! last chance to register is now ! REGISTER NOW

SE_LOG: when AAALR(1072.471418) is greater than 1.000000, we suggest using new row applicator to improve time and mem efficiency.

Andre_Sostizzo
Digital Support
Digital Support

SE_LOG: when AAALR(1072.471418) is greater than 1.000000, we suggest using new row applicator to improve time and mem efficiency.


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 efficiency.
System:     - aggregating on 'EXAMPLE QVW'(%KEY_EXEC_GROUP) with Cardinal(164), for Object: Document\CH431_309715473 in Doc:

Environment:

  • QlikView Server, all versions

 

Cause:


Large, resource-intensive application required a different algorithm in the calculation engine. 

Resolution:


"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 there is a large data set in the QVW which will cause slow response and high memory usage. To remedy this issue, a setting called “DisableNewRowApplicator” can be applied in the Qlikview Server settings.ini (found under C:/Programdata/QlikTech/QlikViewServer). 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. 

The setting needs to be applied in the Qlikview Server Settings.ini file below [Settings 7] property. Qlikview Server will need to be stopped in order to make this change and restarted after the Settings.ini file has been modified.  Please see example Settings.ini file below: 
 

[Settings 7]
DisableNewRowApplicator=0
...

AAALR-DisableNewRowApplicator.gif

 


Note: In a multi-nodes environment, the settings needs be added in the Qlikview Server Settings.ini file for each node.

Possible settings:
DisableNewRowApplicator=1: use Engine default.
DisableNewRowApplicator=0: use new row applicator where Engine deems suitable.
DisableNewRowApplicator=-1: force to use new row applicator all the time. (Only available in Qlikview 11.20 SR16 and higher)


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 eliminating 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 there is no noticeable performance issue, 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, it is necessary to monitor if the environment performs better or worse after the setting has been enabled.


 

 
Labels (2)
Version history
Revision #:
4 of 4
Last update:
‎2020-12-02 10:49 AM
Updated by: