“Can You Optimize This Qlik Sense App?” — Qlik Just Asked You the Same Question

Read time: 2.5 minutes

How to Identify the Real Reason Your Qlik Sense Application Is Slow

1. Optimizing a poor data model will not resolve any issues.

• Synthetic keys

• Circular references

• Different grains of data

The issue here is that if the associations aren't created correctly, then the performance is simply a byproduct of the poor association.

2. Your load script is doing too much.

• Endless joins

• Resident loads everywhere

• Transformations hidden within transforms

Shift:
Script heavily to clean up your upstream pipelines and use simpler data modeling.

3. The front end is overloaded with data.

• Too many fields on the screen

• Too many charts on the screen

• Too many links from the front-end interface

The problem here is that if users try to explore data without the structure of the association, it slows down both the user experience and the overall performance of the system.

4. You are designing for "everything" instead of one decision.

• Multiple use cases exist within one application.

• There is no clear flow for users to follow.

Shift:
Change from all-purpose dashboards to decision-specific applications.

5. You are treating the symptoms instead of the causes.

• Caching and performance tweaks in one area

• Small fixes to performance issues

The problems need to be fixed at the foundation, or no amount of modification will resolve them.

💡Key Takeaway: 

Your architecture needs "optimization" but Qlik doesn't.