article AAALR is registered in the Qlik Sense logs in Official Support Articles

AAALR is registered in the Qlik Sense logs

Andre_Sostizzo — Sun, 31 Oct 2021 23:00:27 GMT

The following messages will appear in the engine trace system logs:

QVGeneral: when AAALR(63.312046) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency.
QVGeneral: - aggregating on 'RecruiterStats'(%DepartmentID) with Cardinal(87), for Object: in Doc: ffe8a825-b52e-4ceb-aea2-30de0f2c3306

There has also been reports of end users seeing the message "Internal Engine error" when opening apps when the error above is present.

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

Environment:

Qlik Sense Enterprise on Windows, all versions

"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 results 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, Qlik Sense has a setting called DisableNewRowApplicator (default value is 1).

By setting this parameter to “0”, Qlik Sense 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.

Changing this setting when they have AAALR warnings, making this change has resulted in drastic performance increases.

Possible setting values for DisableNewRowApplicator:

1 - Use Engine default
0 - Use new row applicator where Engine seems suitable
-1 - Force new row applicator all the time

Resolution:

Stop all Qlik Sense services from the windows control panel / services
Locate the “C:\ProgramData\Qlik\Sense\Engine\Settings.ini”
Add this portion to the Engine Settings.ini file (press <enter> at the end of DisableNewRowApplicator=0 so the cursor rests on a blank line below it)

[Settings 7]
DisableNewRowApplicator=0
<---- the cursor should be here when saving the file

Restart all Qlik Sense services
(If multinode) Complete the above steps on every node.

Re: AAALR is registered in the Qlik Sense logs

AdamBS — Wed, 31 Jan 2024 14:20:29 GMT

Thanks for the article. On the Resolution you state the setting must be done on each node in a multi-node environment. Is this 100% necessary? If I have one node dedicated to the large Apps, would it hurt the system if only this node is set to force the New Applicator?

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Mon, 05 Feb 2024 12:51:32 GMT

Hello @AdamBS

We generally advise settings to be identical across nodes. Especially when it comes to settings done in configuration files, rather than settings exposed per node in the management console.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

Albert1177 — Mon, 04 Mar 2024 13:54:58 GMT

I guess this parameter in settings.ini is not persisting in case of version or patching level upgrade of the QS node, and therefore must be set again after a version upgrade - please confirm? Thanks.

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Mon, 04 Mar 2024 14:26:24 GMT

Hello @Albert1177

While defaults can overwrite some .config file modifications, the engine settings.ini will retain all its values post-upgrade. Just tested it on a Nov 2023 to Feb 2024 upgrade.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

henrikalmen — Wed, 24 Apr 2024 12:13:52 GMT

Searching the forum I conclude that this NewRowApplicator algorithm has been around since at least 2015 in QlikView. Why is it still disabled per default in 2024 in Qlik Sense? Is there a downside / potential risk in setting the flag to 0 (or even -1)?

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Fri, 26 Apr 2024 08:53:56 GMT

Hello @henrikalmen

Let me reach out internally to get you an answer for this. Though please note that I will be out of the office for two weeks and my response may be delayed because of this.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

henrikalmen — Tue, 21 May 2024 11:36:53 GMT

@Sonja_Bauernfeind I thought I'd try to bump this thread again and see if it's possible to find an answer to my question?

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Tue, 21 May 2024 13:02:15 GMT

Hello @henrikalmen

I have returned to work; let me follow up on this.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Tue, 04 Jun 2024 14:06:53 GMT

Hello @henrikalmen

Here is the answer: The reason for the NewRowApplicator is not enabled by default is down to how the engine default will function better for the majority of documents. While the NewRowApplicator will improve performance for specific (complex) documents, it does not benefit the majority of documents.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

henrikalmen — Tue, 04 Jun 2024 14:16:45 GMT

Thanks @Sonja_Bauernfeind for investigating this!

I do get the warning as described in the above post in our logs, but when enabling the NewRowApplicator in our development environment (same hardware and setup as our production environment) I can't really see an improvement in calculation time or anything like that, so perhaps I should just leave this parameter with its default value in the production environment.

Re: AAALR is registered in the Qlik Sense logs

Huiying — Fri, 08 Nov 2024 11:58:16 GMT

Hei @Sonja_Bauernfeind
We have DisableNewRowApplicator=0 on all our customer facing engines, but not on the central nodes.
We still get lots of AAAL errors in our logs.
Is it because the central nodes don't have DisableNewRowApplicator=0?
If enabling it is not preferred for small apps, why it has to be applied to the whole cluster, instead of dedicated engines? I don't get it...

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Thu, 14 Nov 2024 06:52:13 GMT

Hello @Huiying

Let me forward this to our engine experts!

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

Sonja_Bauernfeind — Thu, 14 Nov 2024 13:13:12 GMT

Hello @Huiying

The setting must be applied on all nodes, including your central node. To further investigate the reason for the AAALR log entries, we recommend using the App Metadata Analyzer.

See App Metadata Analyzer (help.qlik.com and App Metadata Analyzer (Windows).

If you need more direct assistance, please post your request directly in App Development. Our Professional Services can also be engaged to help you further.

All the best,
Sonja

Re: AAALR is registered in the Qlik Sense logs

Huiying — Fri, 15 Nov 2024 08:02:21 GMT

Thank you, Sonja! 🙂

Re: AAALR is registered in the Qlik Sense logs

Huiying — Fri, 15 Nov 2024 08:19:19 GMT

another question @Sonja_Bauernfeind :
will DisableNewRowApplicator=0 be available in Qlik Cloud?
I mean, if we rely heavily on DisableNewRowApplicator=0, when we move to Qlik Cloud, will we have big trouble?

article AAALR is registered in the Qlik Sense logs in Official Support Articles

AAALR is registered in the Qlik Sense logs

Environment:

Resolution:

Related Content:

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs

Re: AAALR is registered in the Qlik Sense logs