topic Re: Calculated Dimension and conditional dimension --> bad performance in QlikView

Calculated Dimension and conditional dimension --> bad performance

peschu123 — Tue, 20 Aug 2013 09:05:05 GMT

Hi,

I use a calculated Dimension like this in my straight table:

"=IF(Relevant=1 AND Ontime=0 AND Datetype='DRD',%Order)"

This worked pretty well in the past without any significant impact on performance.

Now I added a condition to show columns (or not) based on a selected field(this thread).

1. If I remove the calculated dimension and use instead conditional show for the chart it works a bit faster, but is not very userfriendly.

Is there any way to remove the calculated dimension and set those values for the chart instead? I don't know if it would be faster to use the values with set analysis in every expression?

The calculated dimension has another side effect, which makes it impossible to remove the (previous) selection by clicking the cell/field again.

2. With the conditional showing of columns, the tables updates on every little change of size, or selection of other values.Is it possible to supress the automatic refresh? Normally its not a problem. But with the perfomance issues it is extremely laggy and annoying.

Thank you in advance for your help.

Re: Calculated Dimension and conditional dimension --> bad performance

sparur — Tue, 20 Aug 2013 11:26:19 GMT

Hi Peter

As I know, calculated dimension usually have a big impact on performance (especially with huge data). So I recommend try to use set analysis for restrictions. usually it helps.

as for the second question, I think it's impossible, because the system usually re-calculated each objects. You can find more details in this article: http://community.qlik.com/blogs/qlikviewdesignblog/2013/07/15/logical-inference-and-aggregations

Re: Calculated Dimension and conditional dimension --> bad performance

peschu123 — Thu, 22 Aug 2013 08:47:01 GMT

Hi Anatoly,

thank you for your reply.

The second point I mentioned, is solved. I put the file on the server and in Browser and AJAX there is no "crappy" behavior. Everything works smooth. It just appears on my local workstation.

You think its more efficient to make the restrictions via set analysis in every expression instead of a calculated dimension?

Regards,

Peter

Re: Calculated Dimension and conditional dimension --> bad performance

sparur — Fri, 23 Aug 2013 05:29:23 GMT

Hi Peter.

Usually yes.

Re: Calculated Dimension and conditional dimension --> bad performance

peschu123 — Fri, 23 Aug 2013 09:41:01 GMT

Ok. I will check that in future.

What if I use no aggregation function, than I have to use IF - Statements?!

Re: Calculated Dimension and conditional dimension --> bad performance

sparur — Fri, 23 Aug 2013 10:18:20 GMT

Even if you don't use aggregation functions in expressions, the system still does it for you You can find more details about this here: http://community.qlik.com/blogs/qlikviewdesignblog/2013/08/06/it-s-all-aggregations

Re: Calculated Dimension and conditional dimension --> bad performance

peschu123 — Tue, 27 Aug 2013 07:27:16 GMT

Thank you for that link. Improves quality of scriptcode