topic Re: Peformance issue in QlikView

Peformance issue

Fri, 19 Sep 2014 14:01:32 GMT

Hi,

I'm facing performance issue in line chart, the dimension that i was using the "Date&' '&Time". My app containing huge amount of data its nearly 40 million rows.

Can anyone helps me in optimizing the performance in this chart.

Satish

Re: Peformance issue

MK_QSL — Fri, 19 Sep 2014 14:06:07 GMT

If you are used it as a Calculated Dimension, better to create in the script itself...

Re: Peformance issue

Fri, 19 Sep 2014 14:46:31 GMT

Hi,

Actual calculated dimension that i used in the app as below :

CaptureDate&' '&IF(Len(Date(CaptureDate))>0,Pick(WildMatch(CaptureTimeSPCRange,'5','10','15','20','25','30','35','40','45','50','55','60'),[5mins],[10mins],[15mins],[20mins],[25mins],[30mins],[35mins],[40mins],[45mins],[50mins],[55mins],[60mins]),'')

Note : here CaptureDate is from one table and the other columns like [5mins],[10mins].. are from different table.

To write above calculated dimension i needs to join the 2 tables, if we are inner joining the 2 tables for 40 million rows, does it cause performance problem ?

Satish

Re: Peformance issue

MK_QSL — Fri, 19 Sep 2014 14:52:13 GMT

Sorry but Can't tell you without actually working on your apps.. Better you can try at your end....

Re: Peformance issue

Fri, 19 Sep 2014 14:58:08 GMT

Hi,

I tried here in my app by inner joining the 2 tables, the script has reloaded successfully without having script performance issue. But my calculated dimension will vary based on slider selection i.e. if the variable "CaptureTimeSPCRange" is set to 5 then it dimension should be CaptureDate&' '&[5mins], if variable is set to 10 then CaptureDate&' '&[10mins], ...

so we can't control this variable change through editscript right !!!.

Is there any approach that we can proceed ?

Satish

Re: Peformance issue

sundarakumar — Sat, 20 Sep 2014 13:39:24 GMT

Create master time calendar as described below

http://community.qlik.com/blogs/qlikviewdesignblog/2013/07/23/the-master-time-table

I would suggest a more aggregated level would perform best here. Please do not use calculated dimensions in this case.

Hope this helps.

-Sundar