Solved: Re: What is New Row Applicator ? - Qlik Community

fredericvillemi · ‎2015-01-12

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

Emmanuelle__Bustos · ‎2016-09-05

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.

View solution in original post

marcus_sommer · ‎2015-01-12

I don't know but I assume that one/some field(s) have more than 1000000 distinct values or means something similar. Best would be you have a look on your datamodel - per tableviewer and structur-table (it exists already - see new create new objects) - and if try to reconsider the datamodel:

The Importance Of Being Distinct

- Marcus

fredericvillemi · ‎2015-01-13

Well, i thought it was the good answer but i have checked this field as soon as i have seen this message and it was mentionning a key column with 7 distinct values. But as it is a key maybe i uses all tables using this key to make this warning.

I will make a ticket to Qlik to try and have an answer about how this warning should be handled

Thanks

jerrysvensson · ‎2015-01-27

My log says:

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

Even worse I guess. 🙂

Have you heard anything from Qlik?

fredericvillemi · ‎2015-01-28

I still have not created an example file sorry, i'll try to tell it here when it's done and i have an answer

Anonymous · ‎2015-02-11

I just ask Qlik Support the same question, but they couldn't really give any detailed answer. That's what I got back:

"The entry "SE_LOG: when AAALR(1614907703) is greater than 1.000000, we suggest using new row applicator to improve time and mem efficiency. " gives a suggestion that the document that this refers to could be optimized to get better performance. "

There is no specific detail in this. Sorry.

Emmanuelle__Bustos · ‎2015-04-13

Same for me in a QVS 11.2 SR10:

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

Information SE_LOG: aggregation on 'Tramites'(llaveservidor), dstCardinal(3) and AAALR(2.680000).

Any advice?

mongolu · ‎2015-10-14

QVS 11.2SR11 Win2003x64/64GB RAM

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

Besides these posts,i'm interested in this part "we suggest using new row applicator to improve time and mem effeciency".

What does it mean by "row applicator" and how it can improve time and mem efficiency?

Somebody has to put some light into this.

swuehl · ‎2015-10-14

Can't personally add something to this, but a search in the forum reveals a new post from JoeSimmons with some more detailed information:

SE_LOG: when AAALR(6.186927) is greater than 1.000000, we suggest using new row applicator to improv...

mongolu · ‎2015-10-14

I see it has a solution but we don't know more details.

Thank you for your fast answer.