Loading data slowly into table and error calculation timed out'

[Sai_Mohan]

Hi team ,

I need a help in Qlik sense.

I have a report, which has more sheets in it. One of the sheets has table(10 columns) and few filters in it.  Since 2 years, it was working properly. Now, Suddenly this report is loading data very slowly(takes 2 mins) and sometimes it throws error saying ' Error - Calculation timed out', after loading for few mins. Please feel free to give me suggestion how to fix this.

Thanks in advance,

Sai.

[Vegar]

My first thought I get when reading your post is that it is caused by resource limitations. Your application does not have enough cpu or ram to respond quickly. 

Do I understand you correctly that the other sheet are working fine?

If so then my best guess is that your number of unique dimension combinations have increased causing an increase in the number of lines in your table. Qlik calculates each row on the fly as you navigate and select in your app. If you have a table with millions of rows, then Qlik will need to calculate all these rows every time you go to that table. How does the table behave if you make selections so your number of rows gets decreased?

Another possible cause could be changes to the data model or changes to the measures you use in that table. Some datamodels and measures are more resource intensive to calculate than others.

A third cause could be that other services in your environment are using your ram/cpu, causing the sudden decrease in performance in your app. (If you are running Qlik on a virtual machine , then it is good if you have disabled resource pooling/sharing on that machine.)

[Sai_Mohan]

Thanks for the reply @Vegar!

If I filter any value, Data shows up immediately. but not the whole data.

I havent done any changes to that report since 3 years, it failed suddenly.

One more thing, I have restricted data to last 3 months. For example. Data should show up from Sep, Oct, Nov.. but It shows april, may  data as well.

Please give me a solution

[marcus_sommer]

It's quite unlikely that a normal growing data-set is causing such effects else you should notice rather small increases on the response-times if there are now some months more of data.

Therefore it's more likely that the data-set itself is different maybe because any join is broken and there are now much more data included and/or any associations between the tables in the data-model or with the used fields in the object are invalide.

This means I would start with a check of the data-model / data-set and if there are changes between the current one and the previous and working releases.