Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Highlighted
Not applicable

Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?

I've been limiting the number of returned results in a table with two different approaches - either by using a calculation condition or using RANK/MAX in the expression.  In terms of system resources and calculation time, which is worse?  My assumption is that RANK/MAX would consume far more resources than a calculation condition, but I was wondering why that is.  If my Calculation Condition is such that I require a certain minimum number of records before the expressions are run, isn't it just as taxing for the system to evaluate the entire dataset to make sure that condition is met?

1 Solution

Accepted Solutions
satishkurra
Valued Contributor II

Re: Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?

No doubt, Calculated dimensions are resource heavy and takes more time

Also consider the valuable point from Sundeep

View solution in original post

3 Replies
sudeepkm
Valued Contributor III

Re: Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?

you can check your chart's Calculation time and memory consumption from the Sheet Properties > Objects details.

you can consider taking a larger data set and then can check these stats.

satishkurra
Valued Contributor II

Re: Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?

No doubt, Calculated dimensions are resource heavy and takes more time

Also consider the valuable point from Sundeep

View solution in original post

Not applicable

Re: Calculation Condition vs. limiting by RANK/MAX - which is more resource intensive?

Thank you both, I appreciate the tips!