topic Re: performance tunning in qliksense in App Development

performance tunning in qliksense

Fri, 03 Mar 2017 09:44:32 GMT

Basic Steps to Start Performance tunning In qliksense App

Re: performance tunning in qliksense

marcus_sommer — Fri, 03 Mar 2017 11:21:38 GMT

Its not different to qlikview and quite simple: load only the needed records and fields and build an appropriate datamodel. I think this will be helpful: Get started with developing qlik datamodels.

- Marcus

Re: performance tunning in qliksense

Fri, 03 Mar 2017 11:50:29 GMT

Thanks Marcus for Responding,

I have got requirement to tune the App , mainly chart expressions ,

loading charts taking time , and there are expressions used with only IF condition ,

and iam stucked here ...

any furthur investigation is appreciated

Thanks in advance

Re: performance tunning in qliksense

vlad_komarov — Fri, 03 Mar 2017 23:54:11 GMT

Charli Leo,

You did not provide many details about your application (why chart expressions were created with IFs, for example), but I would suggest to invest some time into organizing these expressions with more "classic" Set Analysis, using flags, for example.

Check documentation and videos by mto

A Beginners' Introduction to Set Analysis (video)

Set Analysis - Part 2 - Cool Stuff You Can Do (video)

Regards,

Vlad

Re: performance tunning in qliksense

Michael_Tarallo — Sat, 04 Mar 2017 01:33:53 GMT

Hello Charli,

A proper data model is the key as pointed out by Marcus and Vladimir has some good points too depending on what is being processed.

You can also try this instead of nested IFs.

For example this:

if(wildmatch(PRODNAME,'*Sony*'),'Sony',  
if(wildmatch(PRODNAME,'*Toshiba*'),'Toshiba',  
if(wildmatch(PRODNAME,'*Samsung*'),'Samsung','Other')))

Can become:

IF(wildmatch(PRODNAME,'*Sony*','*Toshiba*','*Samsung*')>0,
PICK(wildmatch(PRODNAME,'*Sony*','*Toshiba*','*Samsung*'),'Sony','Toshiba','Samsung'),
'Other')

HTH

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

Regards,

Mike

Qlik