Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Highlighted
Chanty4u
Esteemed Contributor III

Metric Performance issue

We are trying to create a metric-- ignoring all the filters in the layout except for two FIELD1,FIELD2

we are able to get the correct data. Using the following expression

Count(Distinct TOTAL<FIELD1,FIELD2>{1<FIELD1=$::FIELD1,FIELD2=$::FIELD2>}USERS)

But we run into serious performance issues.

There are two tables TABLEA contains FIELD1 and has 15million rows

TABLEB contains FIELD2 and has 1million rows

Both these tables are joined on USERS id. Please suggest an alternatice approach to get the same result with better

performance

Thanks in advance

7 Replies
MVP
MVP

Re: Metric Performance issue

MVP & Luminary
MVP & Luminary

Re: Metric Performance issue

I think you should consider to change your datamodel and transfer both fields into a single table then otherwise will be the virtual table which needs to be created very large, see also: Logical Inference and Aggregations.

- Marcus

MVP
MVP

Re: Metric Performance issue

In which context are you using this expression? Chart (type)? Dimensions?

Re: Metric Performance issue

I am assuming you have both Field1 and Field2 as dimensions in one table which might be creating a massively huge table which might be causing the issue

May be join the two tables in the back end to get a better performance on the front end

Chanty4u
Esteemed Contributor III

Re: Metric Performance issue

Hi Swuehl,

We are using this expression in a measure which is used in a pivot table.

Chanty4u
Esteemed Contributor III

Re: Metric Performance issue

Hi Sunny,

We tried combining the Table 1 and Table 2 which has resulted in a huge data set. Which lead to considerably long load time.

We would really like to keep the backend tables as is,

Is there any alternate expression that we could use in the measure to improve the performance but get the same result set.

Re: Metric Performance issue

I guess it comes down to a choice between back end load time vs. front end performance