What is New Row Applicator ?

[fredericvillemi]

Hello,

i have just installed 11.2SR9 on our production server and in the logs we can now see optimization tips like this one :

Warning

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

What does it mean ? what is this new row applicator ?

Thanks

[tseebach]

Hi Fredric,

If you're using the governance dashboard and the Warning level, then try to look at the message with the same timestamp which is 700. This message shows what fields is causing it.

[reanfadyl]

‌Hi Torben, we have this issue coming up for a small number of fields in our data model. Do you have any advice on what you did next to resolve the issue?

[pablolabbe]

Do you have any update on this issue ?

[Emmanuelle__Bustos · Accepted solution]

Hi Pablo,

according with Qlik Support I opened a case and the solution was:

The warning to which you are referring - QVGeneral: when AAALR(1.293973) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency. AAALR" is a very low level concept deep in the QlikView engine. Generally speaking it means the average length of aggregation array. The longer this array is, the more RAM usage and CPU power are to be consumed by the engine to get aggregation result for every hypercube node and can thus effect performance.

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.

To mitigate this, you can add the below setting to the Settings.ini file located in the QlikTech\QlikViewServer:

DisableNewRowApplicator=0

By setting this parameter to “0”, QlikView will use an new algorithm which is optimized for large data set to do the aggregation, and will consume much less RAM and CPU power.

[Anonymous]

Sounds promising 🙂

The question ist: why isn't it enabled out of the box, or at least mentioned in the release notes?

Have you got any information if this is a supported easter egg?

[fredericvillemi]

One year ago, you told us to set disable new row applicator = 0

No information have been found about this setting, is it still mandatory to use it for big documents ?

Why is it not the default mode ?

Thanks

[Emmanuelle__Bustos]

Accordin to Qliktech support:

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.

To mitigate this, you can add the below setting to the Settings.ini file located in the QlikTech\QlikViewServer:

DisableNewRowApplicator=0

By setting this parameter to “0”, QlikView will use an new algorithm which is optimized for large data set to do the aggregation, and will consume much less RAM and CPU power.

I guess it's not default because only affects large data sets environments.

[fredericvillemi]

Ok thank you

Too bad they don't use more explicit messages or enforce the algorithm designed for large data when needed

Thanks

[Anonymous]

Hi!

In the meantime the Qlik Support Knowledge Base article is quite clear about this setting.

See below if you might have not read about it!

[fredericvillemi]

Hello,

thanks

yes I have made a ticket and got this article. It's clear. I still don't know why they don't use the new algorithm by default but well, I have defined the setting Disable=0 on my test server and I don't have the message anymore about AAALR

It seems to use less memory too but I need to wait for users to try it to confirm it's far better than before.

Thanks