topic Re: Advanced performance tuning techniques into QV. in QlikView

Advanced performance tuning techniques into QV.

Fri, 20 Nov 2020 18:02:30 GMT

Dear all,

Please give me good Ideas about,

QlikView Application level (UI), Publisher level and Server lever (QVS) -Implementing the performance tuning and advanced performance tuning techniques using into QV. Any documentation into existing.

Regards,

Raja.

Re: Advanced performance tuning techniques into QV.

giakoum — Thu, 06 Feb 2014 08:25:47 GMT

hope this helps!

Re: Advanced performance tuning techniques into QV.

Thu, 06 Feb 2014 08:51:45 GMT

PFA

Re: Advanced performance tuning techniques into QV.

Thu, 06 Feb 2014 08:55:58 GMT

Hi Loannis,

Thanks for your replay,

I have above documents.

Please bit elaborate common steps are generally for into QV development like avoided the complex query, avoided nested loops, unused fields, avoid synthetic key, avoid the unused tables, avoid more dimension fields and more record into Pivot table and straight table,use GRID container object like that.

Regards,

Raja.

Re: Advanced performance tuning techniques into QV.

giakoum — Thu, 06 Feb 2014 08:56:18 GMT

Do you need VMWare settings also?

Re: Advanced performance tuning techniques into QV.

Thu, 06 Feb 2014 08:59:56 GMT

Hi Venkat Reddy and Loannis Giakoumakis,

Thanks for your prompt replay sir.

Regards,

Raja

Re: Advanced performance tuning techniques into QV.

Thu, 06 Feb 2014 09:48:46 GMT

To improve the performance of Qlikview follow this

- Load only required fields remove unused fields from data model, so that the qlikview file is automatically reduced

- Truncate Time part in date fields, if time is not used in your dashboard.

- Load only required data, ie., if your users analyse only past 3 years data, then load only latest 3 years data instead of loading entire data.

- Do all the calculations required in script itself, insteady dynamically at runtime.

- Avoid using If, try using set analysis.

- Don't display all the charts at once in dashboard, show and hide charts based on the button clicks, so that extra time of loading hidden charts is reduced.

- By default sort the data in script itself, and in dashboard select Load Order, it is optimized one.

- Star Schema is the best data model, it reduces the number of joins.

- Sufficient RAM is required, if file size increased, consider this also if it is not possible to reduce data.

I hope it helps you

regards

Mahesh T