The Document Analyzer Compare Tool

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
DocumentAnalyzerResults_appname_YYYYMMSS_hhmmss.QVD

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:

Expression contents:

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.

-Rob

 

Share

15 thoughts on “The Document Analyzer Compare Tool”

  1. Rob, do you know if there’s any tool like this one available to analyze Qlik Sense apps? We used to use this one a lot in the QlikView days and nowadays we miss it for Sense 🙁

    1. Document Analyzer, and the DA Compare tool, do not use or retain any of the application data from the QVW.

    1. Set the “Save Results to QVD” option to “Yes” as shown in the first image of this post.

  2. Hi Rob,

    we are doing performance assessment on two different version of a Qliksense apps having around 20 sheets.

    I duplicated Doc Analyzer so I can use DocAnalyzer1 on first version and DocAnalyzer 2 on second app. We want to run these apps in parallel on a daily basis for atleast a month until we improve our performance with various performance improve techniques.

    the challenge I’m facing here is not able to dublicate the connections so I can use connection 1 in Doc analyzer 1 and Connection 2 in Doc analyzer 2.

    Thanks
    Raj

    1. You can use different names for the connections and update the CONNECT statements in the script.

  3. I followed the instructions to download the app – unfortunately the Document analyzer loads in notepad – and doesn’t work.

    I have tried unzipping the file many… times, but have been unable to launch the analyzer to evaluate QlikView qvw.

    1. Hi Dorothy,
      Can you please provide the name of file file you are trying to unzip? And the name(s) of the files produced by the unzip?

  4. The problem is not the file – but the application download. These are the steps I followed in QlikView Document Analyzer Cook Book (green Icon box:
    (1) clicked on DocumentAnalyzer_v3.10.zip
    (2) File loaded to my C:\ drive – in zip format
    (3) Right clicked on zip file – selected – extract all
    (3)DocumentAnalyzerBundle appears in directory
    (4) clicked on DocumentAnalyzerBundle – four files appear
    the file: DocumentAnalyzer_V3_10.qvw – is in notepad format(unable to open up in QlikView – to analyze a qvw)

    1. Hi Dorothy, I just tested and it works ok for me.
      1) Is QlikView installed?
      2) What happens if you first launch QlikView, and then use menu File > Open to open DocumentAnalyzer_V3.10.qvw?

      1. Your suggestion to first open Qlikview – then launch the Document Analyzer – works perfectly! Thanks so.. much for all your help!!

Leave a Reply to Rob Wunderlich Cancel reply

Your email address will not be published.