Have you ever had a Qlik Sense Visualization take longer to calculate than you like? You may have been measuring the response time with QSDA (or the older QVF QS Document Analyzer) , Add Sense or a stopwatch.
Your chart is likely made up of several expressions — Measures, color expressions, maybe reference lines. Which expression(s) are the hogs? Some? All?
In QSDA Pro version 1.4 I’ve introduced a “Viz Deconstruction” feature that calculates each chart expression individually and lets you see where time is spent. In the QSDA Pro Viz page, click the button under a Viz:
Clicking the button will pop up the Viz Deconstruction dialog. Each expression in the chart will be executed and reported individually.
For this chart I can see that one Measure takes much longer than any other expression. Now I know where to focus my efforts if I want to improve response time.
Here’s another example. Big chart, lots of data, seven Dimensions.
The Measures require over seven seconds each to generate 7M+ output rows. Maybe less detail would result in better performance and a more usable chart. I’ll uncheck a few Dimensions and
Wow! Big improvement in calc time and a more manageable number of rows.
As a final example we’ll see that long calc times are not always due to Measures.
The Measures take only a few milliseconds to calculate. But the color expression takes more then 1/2 second. Can we do this coloring more efficiently?
You may already be deconstructing charts by making clones, commenting code and remeasuring. Of course, you have to deal with the effects of caching and cleaning up after yourself. QSDA Pro provides a much faster and more structured approach.
QSDA Pro is free to try with applications containing 100 or fewer objects. If you want remove the limits, get support or acknowledge the value you get from QSDA, purchase a Monthly or Annual subscription.
I hope you find the Viz Deconstruction feature useful. I have!
Note: There was a bug in the 1.4.0 version that kept the Deconstruction feature from calculating when using a DESKTOP Connection. This has been fixed in version 1.4.2.