We have a Qlikview doc which is about 9MB. It only has two charts, one pulling data from the job_detail table and another pulling from the claims table. See attached data model picture. When users click the claims chart, it always threw 'out of object memory' error on page. The claims table contains about 123k rows of data and the chart displays 8 columns. In my opinion, this data amount is not that large which could cause memory issue. Where the problem is? Any suggestion are appreciated.
Qlik associates fields automatically by an equally name without any consideration of the content. If the relationship between these key-fields isn't 1:1 else 1:n or even n:n it increased the number of (possible) records/rows. It's in the UI quite the same as by joining tables in the data-model.
Especially n:n relations are critical - not only in regard to any performance-aspects else also to the view-results. Even more problematic is if the keys have no common data, for example one is a number like 1 - 12 for the months and the other is 'Jan' to 'Dec' which won't be matching even if the main-information the same.
Yes, it's not related to the size of the data-set else to the way the charts are designed. I assume that there are fields included which have no proper association to each other - which would cause some kind of cartesian product which may hit the object RAM limitation.
Qlik associates fields automatically by an equally name without any consideration of the content. If the relationship between these key-fields isn't 1:1 else 1:n or even n:n it increased the number of (possible) records/rows. It's in the UI quite the same as by joining tables in the data-model.
Especially n:n relations are critical - not only in regard to any performance-aspects else also to the view-results. Even more problematic is if the keys have no common data, for example one is a number like 1 - 12 for the months and the other is 'Jan' to 'Dec' which won't be matching even if the main-information the same.
