In my consulting practice, I’m frequently engaged to improve the performance of one or more QlikView applications. In addition to an improved application, I typically deliver a report of measured improvement and what was changed to achieve the improvements.
I use the Document Analyzer tool as my tuning workbench. I’ve developed, and made available as a free download, a companion “Document Analyzer Compare Tool” that automates the comparison and reporting of different Document Analyzer runs. You can download both tools from the QlikView Cookbook Tools section. Let’s look at the details.
Document Analyzer v3.0 introduced an option to save analysis results to a QVD.
When set to “Yes” a reload of DA will create a results QVD named
The results QVD qill be created in the same directory as Document Analyzer.qvw.
The “Optional Analysis Title” will be included in the QVD. Use this label to identify the phase of your tuning or developement work such as “baseline” or “final”.
The DA Compare Tool can consume and report on these result QVDs. To load results, open DACompareTool.qvw and enter a directory path on the “Main” sheet. Press the “Load Result QVDs” button and the directory will be scanned for result QVDs.
A summary table will show what result QVDs were loaded. Note that each version of the DACompareTool requires results from a minumum version of Document Analyzer. DaCompareTool v1 requires Document Analyzer v3.3 or later. Results from versions earlier than the minumum will not be loaded but will be reported in log messages.
The “Trending” sheet will display gross performance metrics for all results loaded. You can if course filter which results appears on these charts using listboxes.
The remaining sheets are the “Compare” sheets, which compare two result sets. The compare sheets use a naming common to “diff” programs — one result is selected as the “Left” side and another as the “Right”. Left/Right reflects their position in the comparison charts.
On any compare sheet use, the “Select Analysis” button to select two analyses.
Close the Select Analysis dialog by clicking the X in the upper right of the dialog. This will lock your Left/Right selections.
Throughout the UI, data associcated with “Left” will be light green and “Right” will be light blue.
Now that two results have been selected, various comparisons are available. Items associated with only one side will be highlighted in the associated color. You can compare and filter
Object Calculation times:
Script Tabs and Lines:
Table Names and Sizes:
The orange color indicates that both side contain the named table, but with a different row count.
I’ve also included a “Server RAM” sheet that can be helpful in computing the RAM required for a set of QVWs. You will still need to add in estimated cache requirements, but it’s a good starting point.
“Concurrent User Sessions” is an input field allowing you to model an estimated number of concurrent users for each document.
DACompareTool looks best if the Open Sans font is installed. If Open Sans is not installed, you’ll see a warning on the “Introduction Sheet”. It will still work without Open Sans, just not as pretty You can download Open Sans from google fonts.
If you do performance tuning, I hope you find the DACompareTool useful. Let me know in comments here or on this site’s contact form if you have suggestions or questions.
I’ll be diving deeper into Document Analyzer and the Compare Tool at my Feb 2 “Document Performance Tuning” class and in an expanded Performance Tuning session with Oleg Troyansky at the 2017 Masters Summit for Qlik. I hope to meet you at either or both for a deep dive into the principles and practice of Qlik performance.