qlik hardware benchmark...qlik hardware benchmark | 4 [qlikview] download the hw bm test app,...

Q L I K . C O M

Qlik

Hardware

Benchmark Version 1.0

P u b l i s h e d : S e p t e m b e r , 2 0 2 0

Qlik Hardware Benchmark | 1

TABLE OF CONTENTS

Introduction 2

Setting up the Hardware Benchmark Test 3

Prerequisites – What You Need 3

Downloading Hardware Benchmark Files 3

Setting up the Qlik Product Server 4

Setting up the Load Client Machine 8

Running the Hardware Benchmark Test 12


Running the Hardware Benchmark Test 12

Description of the different tests included in the HW BM package 14

1. Low Load Test 14

2. Low Load – Cached Test 14

3. High Load Test 14

4. Cached Tests 14

5. Single threaded Test 15

6. CPU Capacity 15

Analyzing the Hardware Benchmark Test Results 16


Downloading Files 16

Collecting the Hardware Benchmark Test Results 16

Preparing the Analysis of the Hardware Benchmark Test Results 16

Submitting the Hardware Benchmark Test Results for Review 17


Introduction

Thank you for your interest in how Qlik Sense® and QlikView® perform on different hardware

platforms!

The Qlik® Scalability Center in Lund, Sweden, created the Qlik hardware benchmark test package to

help organizations like yours validate the performance of their hardware against that of similar

environments. The test results are also used as input for recommendations regarding well-

performing hardware.

This document describes how to configure and run the Qlik hardware benchmark test in your

environment, and how to analyze the test results. Note that the test only supports Qlik Sense

Enterprise on Windows and QlikView Server 12 or newer.

In this document the annotations [QlikView] and [Qlik Sense] will be used to show that it is only

relevant for QlikView or Qlik Sense respectively. If no annotation is used, it is valid in both cases.


Setting up the Hardware Benchmark Test

This section describes how to set up the HW BM (hardware benchmark) test.

Prerequisites – What You Need

Hardware

• Windows server (referred to as “Qlik product server” below): This is the hardware to be

tested. It should be set up as a clean single node installation of Qlik Sense Enterprise or

Qlikview Server for the HW BM test. See the Setting up the Qlik Product Server section for

more information.

• Windows client PC with at least 8GB of RAM and a fast network link to the Qlik product

server: This machine is used as load client during the hardware benchmark test. See the

Setting up the Load Client Machine section for more information.

Software

• [Qlik Sense] Qlik Sense Enterprise on Windows: To be installed on the Qlik product server.

• [QlikView] QlikView Server 12 or later: To be installed on the Qlik product server.

• Qlik HW BM package

• HW BM test app: See the Downloading Hardware Benchmark Files section for information

on how to download it.

• Google Chrome web browser: Used on both the Qlik product server and the load client

machine.

• Windows PowerShell 4.0 or higher: Used on the load client machine. See the Setting up the

Load Client Machine section for more information.

• [Qlik Sense] The gopherciser command line tool that is included in the Qlik Sense

Enterprise Scalability Tools.

• [QlikView] Apache JMeter™

Downloading Hardware Benchmark Files

Download the software listed in this section before setting up the Qlik product server and the load

client machine.

HW BM Package

The zip-archive (HWBM-Package-1.0.zip) contains all the scripts needed and can be found on the

Scalability Center SharePoint site:

https://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-

iZjQF0BhO1eM59v9LW2W4EPc92cQw

HW BM Test App

The HW BM test app is used when testing the Qlik product server. The files can be found on the

Scalability Center SharePoint site:



[Qlik Sense] Download the HW BM test app, 200M-PTSalesAnalytics-v3.qvf, from the Qlik

Scalability Center SharePoint site. The file is available in the HW Benchmarking package folder.

https://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQwhttps://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQwhttps://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQwhttps://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQw


[QlikView] Download the HW BM test app, 200M-PTSalesAnalyticsv2.qvw, from the Qlik Scalability

Center SharePoint site. The file is available in the HW Benchmarking package folder.

[QlikView] Apache JMeter™

Documentation, tutorials and source files are available here: https://jmeter.apache.org

Qlik HW BM test for QlikView requires JMeter 4.0. It can be downloaded here:

https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-4.0.zip

[Qlik Sense] Gopherciser

The Gopherciser command line tool is included in the Qlik Sense Enterprise Scalability Tools.

These can be downloaded and found here:

https://community.qlik.com/t5/Qlik-Scalability/Qlik-Sense-Enterprise-Scalability-Tools/m-p/1579916

Setting up the Qlik Product Server

Recommended BIOS Settings

See the http://community.qlikview.com/docs/DOC-2362 document, which is available in Qlik

Community. The document contains information on BIOS settings that are beneficial for the QIX

engine in QlikView and Qlik Sense Server.

Administrator Privileges on the Server

Make sure that the user account used on the load client machine is member of the Administrators

group. This is needed to restart the QlikView or Qlik Sense services, which is automatically done

before each test is started.

[Optional] Creating a Data Collector Set

A Data Collector Set is needed to monitor the resources during the HW BM test. This normally will

be done automatically by the powershell script of the HW BM package. If you prefer to do this step

manually, the template can be found in the PerformanceCounters folder of the HW BM package.

If you wish to do this manually:

1. Start the Server Manager on the Qlik product server and go to Tools > Computer

Management.

2. Expand System Tools > Performance > Data Collector Sets > User Defined.

3. Right-click and select New > Data Collector Set:

a. Enter “QlikSense” in the Name field.

b. Select Create from a template and then Next.

c. Browse to the template, [Qlik Sense] QlikSense10-template.xml or [QlikView]

QlikView10-template.xml, which is available in the PerformanceCounters folder in the

hardware benchmark package and select Open.

d. Select Finish.

e. Select the newly created Data Collector Set and make a note of the path in the Output

column. The path will be needed when collecting the test results.

f. Select the Start icon:

https://jmeter.apache.org/https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-4.0.ziphttps://community.qlik.com/t5/Qlik-Scalability/Qlik-Sense-Enterprise-Scalability-Tools/m-p/1579916http://community.qlikview.com/docs/DOC-2362


Note: Every time the Qlik product server is rebooted, you need to manually start the Data Collector

Set from the Server Manager if the option to do this automatically is disabled in the HW BM

powershell script.

[Qlik Sense] Installing Google Chrome Web Browser

Due to file size restrictions in some web browsers, it is recommended to use the Google Chrome

web browser when importing the HW BM test app into Qlik Sense.

Do the following:

• Download and install the Google Chrome web browser on the Qlik Sense server.

[Qlik Sense] Installing and configuring Qlik Sense Enterprise

First install Qlik Sense Enterprise on the Qlik Sense server as a clean single node (that is, as a

central node) deployment. Then configure it as followed:

Configuring the License

The license must be configured so that the hardware benchmark test, which uses header

authentication, can use the licenses available. This is done by creating a “fake” domain name,

which is used when configuring the header authentication.

Do the following:

1. Open the Qlik Management Console (QMC) on the Qlik Sense server and go to License

and tokens.

2. Select Login access rules > Create new:

a. Enter “Test” in the Name field.

b. Enter “1000” (or more) in the Allocated tokens field.

c. Select Apply.

3. Create a new license rule:

a. Set user to “userDirectory”.

b. Enter “BMTest” (the “fake” domain) as value.

c. Select Apply.

Configuring the Proxies

The hardware benchmark test can only run on port 80, which needs to be enabled (as it is disabled

by default). In addition, a virtual proxy that enables the header authentication is needed.

Do the following:

1. Go to Proxies in the QMC on the Qlik Sense server.

2. Allow HTTP traffic:

a. Select Central > Edit.

b. Select Ports under Properties.


c. Select the Allow HTTP checkbox.

d. Select Apply.

3. Create a new virtual proxy:

a. Select Virtual proxies under Associated items.

b. Select Add > Create New.

c. Enter “header” in the Description field.

d. Enter “header” in the Prefix field.

e. Enter “X-Qlik-Session-header” in the Session cookie header name field.

f. Select Authentication under Properties.

g. Select Header authentication static user directory in the Authentication method

drop-down list.

h. Enter “X-Qlik-Userheader” in the Header authentication header name field.

i. Enter “BMTest” in the Header authentication static user directory field.

j. Select Add new server node and add Central as a load balancing node.

k. Select Apply.


Disabling All Tasks

Do the following:

1. Go to Tasks in the QMC on the Qlik Sense server.

2. Select Actions > Select all rows and then More actions > Disable.

Importing and Publishing the HW BM Test App

Note: It is recommended to perform the import using the Google Chrome web browser.

Do the following:

1. Go to Apps in the QMC on the Qlik Sense server.

2. Import the hardware benchmark test app:

a. Select Import.

b. Browse to the 200M-PTSalesAnalytics-v3.qvf file and then select Import.

3. Publish the hardware benchmark test app to all users:

a. Select the newly imported 200M-PTSalesAnalytics-v3 app and then select Publish.

b. Select Everyone in the Stream drop-down list.

c. Select OK.

[QlikView] Configuring QlikView Server

Before you modify any settings, make sure that the 200M-PTSalesAnalyticsv2.qvw file has been

copied to the QlikView Server machine and, if needed, that the Document folders have been

updated (under System > Setup > QlikView Servers > select the host of the QlikView Server >

Folders).

To use the benchmark package with the provided QlikView document, which contains an embedded

document license, changes in QlikView Management Console (QMC) are needed.

The changes needed in a default QlikView installation are described below. If your installation

differs from default, it is recommended to set the Performance settings back to defaults.

Session Recovery

The Session Recovery setting needs to be changed as JMeter simulates many sessions by reusing

the same users. Recovering from the last state where certain users were active might cause issues

for the predefined script.

The setting is available under System > Setup > QlikView Servers > select the host of the

QlikView Server > Documents tab in the QMC.

De-select the Allow Session Recovery setting.

Logging

The Logging setting is used to change the log level to get more detailed information for the analysis.

The setting is available under System > Setup > QlikView Servers > select the host of the

QlikView Server > Logging in the QMC.

Select the following in the Logging section:

• Enable Session Logging

• Enable Event Logging

Select the following in the Event Log Verbosity section:

• High

As the Event logs grow over time, it might also be a good idea to set the Split Files option to Daily.


Security

For the script to use the document with the embedded license, QlikView Server should be in DMS

mode.

The Security setting is available under System > Setup > QlikView Servers > select the host of

the QlikView Server > Security in the QMC.

Select the following in the Authorization section:

• DMS authorization (QlikView controls the file access)

Document Settings

To use the embedded document license, set the users authorized to access the document and

enable dynamic document CAL assignment.

Go to Documents > User documents > select the host of the QlikView Server > select 200m-

ptsalesanalyticsv2.qvw in the QMC.

Select the Document CALs tab and check that the Document CALs section contains information

on “2000 Embedded Document CALs”. In addition, select the Allow dynamic CAL assignment

checkbox.

In some cases, the Document CALs tab is not present. If so, restart the QlikView Server services to

resolve the issue.

Select the Authorization tab and then the green plus icon next to User Authorized to Access

Document to display a new entry. Set Access to Always and User Type to All Authenticated

Users.

After implementing the changes described above on the QlikView Server machine, open the

AccessPoint using the load client and access the 200m-ptsalesanalyticsv2.qvw file to check if it is

accessible.

Enabling Header Authentication

Go to System > Setup > QlikView Web Servers > select the host of the QlikView web server >

Authentication in the QMC.

Set Type to Header.

The Unpacking and configuring the Qlik HW BM package section below describes how to configure

the Header name value (default value: QVUSER).

Setting up the Load Client Machine

Installing Google Chrome Web Browser

The Google Chrome web browser with the “Modify Headers” extension is used to test the access to

the hardware benchmark test app on the Qlik product server. Note: this can also be done with the

latest Firefox browser.

Do the following:

1. Download and install the Google Chrome web browser on the load client machine.

2. Install the “Modify Headers for Google Chrome” extension in the web browser.

3. Configure the extension as follows:

a. Select + (Add New) to add a new header modification.

b. Select Add in the Action drop-down list.


c. Enter [Qlik Sense] “X-Qlik-Userheader” or [QlikView] “QVUSER” in the Name field.

d. Enter anything in the Value field.

4. Select (Enable All) to enable the configuration.

Validating the Access to the Hardware Benchmark Test App

Do the following:

1. Open the Google Chrome web browser (with the “Modify Headers” extension activated) on

the load client machine.

2. Go to [Qlik Sense] http:///header/hub or [QlikView] http:///qlikview (where

is the hostname of the Qlik product server).

Note: Make sure that the firewall settings on the Qlik product server do not refuse the

connection.

3. Open the hardware benchmark test app ([Qlik Sense] 200M-PTSalesAnalytics-v3 which is

available in the Everyone stream) or ([QlikView] 200m-ptsalesanalyticsv2.qvw), to make

sure that it is accessible.

[QlikView] Install JMeter

Once the binaries have been downloaded (see above), unzip them to a folder of your choice on the

client machine. No further installation is needed.

Configuring the user privileges to run JMeter

In some situations, local administrator privileges are needed to run JMeter from a certain directory,

which might cause problems if not set up properly.

The following actions may help avoiding privilege issues:

• Do not unzip the JMeter download package under C:\, Program Files or any system

directory. Instead, extract it under a directory to which you have read, write and execute

privileges.

• Disable the User Account Control (UAC) settings on the JMeter client machine by selecting

the Start button and then entering “UAC”. Disable UAC by reducing the UAC setting to its

lowest level. Then restart the client machine.

[Qlik Sense] Install Gopherciser

Extract the Qlik Sense Enterprise Scalability Tools to a folder of your choice on the client machine.

The Gopherciser binary (gopherciser.exe) can be found in the gopherciser folder. No further

installation is needed.


Configuring Windows PowerShell

Windows PowerShell is needed on the load client machine to run the hardware benchmark test.

Do the following:

1. Start Windows PowerShell on the load client machine.

2. Check that the PowerShell version is 4.0 or higher using the following command:

$PSVersionTable.PSVersion

3. Ensure that “ExecutionPolicy” is set to “RemoteSigned” using the following command:

Get-ExecutionPolicy

4. If you need to change the “ExecutionPolicy” setting, run PowerShell as administrator and

use the following command: Set-ExecutionPolicy RemoteSigned

Unpacking and configuring the Qlik HW BM package

Do the following:

1. Unpack the Qlik HW BM package on the load client machine. The structure of the resulting

folder is as followed:

File/Folder Name Description

Execute-HWBM.ps1 the powershell script that runs the HW BM package.

Logs will contain detailed logs of the jmeter run when running

towards a QlikView environment.

PerformanceCounters contains the performance counter templates

QV12Scripts contains the JMeter scripts that will run towards the QlikView

environment

Results will contain subfolders for every run of the HW BM package

Scripts contains the gopherciser scripts that will run towards the Qlik

Sense environment

2. Open Execute-HWBM.ps1 in Windows Powershell ISE or in an editor of your choice. Edit the

necessary items in the “MANDATORY SETTINGS” region. Variables in Powershell are set

with a ‘=’ sign and strings should be between double quotes “”.

Variable Description

$ProxyHostname the hostname of the Qlik product Server. (eg. “qlikviewserver”)

$ScriptType Determines which test is run. Set to “QV12” for QlikView HW

BM test or to “gopher” for Qlik Sense HW BM test.

$ToolFolder

[QlikView] points to the full path of the bin folder of jMeter (eg.

“D:\apache-jmeter-4.0\bin”)

[Qlik Sense] points to the full path of the folder where the

Gopherciser executable can be found (eg.

“C:\QlikEnterpriseTools\gopherciser\”)

$WebServerType [QlikView] Webserver version: "IIS" or "QVWS".

[Qlik Sense] not set


$PerfCountInstall

If set to $true: install the performance counters on the Qlik

product server if they are not there yet. If you do not want this

behavior, set to $false.

$PerfCountStart

If set to $true: the script will start and stop the performance

counter on the Qlik product server automatically, this will keep

the log file at reasonable file size. If you do not want this

behavior, set to $false.

$PerfCountCopyFiles

If set to $true: the script will copy the resulting performance

counter file from the Qlik product server to the result folder on

the load client. If you do not want this behavior, set to $false.

$Comment

This will be shown in the analyser app to identify the test run.

Best practice is to add the QlikView or Qlik Sense version that

was tested and some specific HW settings. eg. “QV-

Apr2020,HTon,NUMAon”


Running the Hardware Benchmark Test

This section describes how to run the hardware benchmark test.

The hardware benchmark test usually takes 2 to 3 hours to run, the time needed varies depending

on the hardware and environment.


Prior to starting the hardware benchmark test, it must be set up as described in the Setting up the

Hardware Benchmark Test section.

Running the Hardware Benchmark Test

Do the following:

1. Start PowerShell on the load client machine.

2. Change folder to where you have extracted the HW BM package.

3. Start the hardware benchmark test using the following command: .\Execute-HWBM.ps1

4. The script will check if services on the Qlik product server can be restarted and if the load

tool can be found. If not, an error will be shown.

5. Check that the mandatory configuration variables are correct and then enter Y.

6. The hardware benchmark test starts. During the execution, output is provided in the window.

Note: when running in Powershell ISE, the Gopherciser tool will output a red text with its

version number, this is not an error. ISE will also not interprete the ANSI color codes used in

the output making it harder to read. One solution is to use Visual Studio Code with

powershell extension which will interprete the output from gopherciser correctly.


In Powershel ISE, the output looks like the following:

In Visual Studio Code, the output looks like this:

7. Wait for the hardware benchmark test to finish. The result is found in a subfolder of the

Results folder.

If you need to stop the test execution before it is finished, send Ctrl+C in the PowerShell

window and then kill the [QlikView] java.exe or [Qlik Sense] gopherciser.exe process in the

Task Manager.


Description of the different tests included in the HW BM package

The HW BM test package includes 3 testgroups with in total 8 tests. The test definitions are similar

for both [QlikView] and [Qlik Sense].

Important to note is that the product architecture and the application as well as the test tools are

different when testing Qlik Sense and QlikView. Therefor it is not possible to compare test results

done on a QlikView server and a Qlik Sense server.

1. Low Load Test

The goal of the low load test is to show the server capabilities when using a large app with a single

user in the system, it will show calculation capacity of the CPU at low load. This test consists of

seven iterations of opening the hub and the app and applying random selections with 5 seconds

think time in between that are done by a single concurrent user.

2. Low Load – Cached Test

The goal of this test is to show how good caching works at low load, it will show the basic latency for

the loadclient to get cached results from the server eg. network and memory latency. This is the

exact same test as the low load test and since no restart of the services are done, all results are

cached. The think time in between selections is reduced to 1 second.

3. High Load Test

The goal of this test is to get a complete picture of how well the whole system is performing when

more and more users are using it.The high load test has a continuous growing amount of concurrent

users with very little think time between clicks triggering light calculations. This test takes 72 minutes

and will have 350 concurrent users in the end. It avoids selecting cached values. The complete

system’s bandwidth is tested: The processor needs to calculate every result and since users will

click with little waiting time in between the queue to the processor will build up. The RAM will be

filled up with cached results and when the RAM is full, the processor will be taxed even more while

clearing RAM space to create new sessions and store new results. The more RAM is available, the

later in time this will happen.

4. Cached Tests

This section consists of three related tests:

a. Low throughput – High Cached (LoT-HiC)

This test shows the system’s behavior with 2 concurrent users and without think time in between the

clicks which trigger cached calculations. Selections are static and no randomization on simulated

selections. This test focuses on cache look ups and delivering cached results. What can influence

this test is the memory configuration, the network latency and the processor clock speed.

b. High throughput – High Cached (HiT-HiC)

The same test as above, but with 60 concurrent users. This will tax the network and memory

bandwidth even more and will show if there is a problem with performance for this scenario.

c. UserPush

Maximum 80 concurrent users and compared to the tests above the test scenario in the application

is shorter. All selections are static and thus cached. This will result in many open hub and open app

actions, taxing a different part of the system.


5. Single threaded Test

This test shows the system's behaviour with 1 user making selections that trigger heavy single

threaded operations. It avoids selecting cached values. This will show how a server will perform for

single threaded operations.

6. CPU Capacity

The goal of this test is to tax the CPU of the system as heavy as possible. For this 2 concurrent

users will do 8 iterations of non-cached selections without think time that trigger many parallel heavy

calculations. The test total run time and the average response time will depend mainly on the CPU

capacity of the system. The average CPU usage for engine will be above 80% for this test.


Analyzing the Hardware Benchmark Test Results

This section describes how to get started analyzing the hardware benchmark test results.


• QlikView Desktop.

• HW BM Result Analyzer: See the Downloading Files section for information on how to

download it.

Downloading Files

HW BM Result Analyzer

Do the following:

• Download the HW BM Analyzer package, HWBM-Analyser.zip, from the Scalability Center

SharePoint site:



Collecting the Hardware Benchmark Test Results

The hardware benchmark test results are stored as subfolders in the Results folder of the HW BM

package. Check if the following files are present in every subfolder:

File/Folder Name Description

Gopherciser-Tests.log [Qlik Sense] Describes the total HW BM test

QV-testgroup.log [QlikView] Describes the total HW BM test

hostname-Processes-

date.csv contains the performance counter result

ServerInfo.xml Describes the HW of the Qlik product server and the load

client

Preload*.txt/tsv Preload result files: 4 in total

Test*.txt/tsv Test result files: 8 in total

Do the following: Copy the subfolder (eg. goQSHWBM-sc-2640-22-20200716-181645) to the

Results folder in the HW BM Analyzer package.

[QlikView] If needed, adjust the timezone in QV-testgroup.log: add a line between date; and

EndDate; with: TimeZone;timezonecode

The default timezone is set to Copenhagen. The timezonecode are according to windows and can

be found in the windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

NT\CurrentVersion\Time Zones

Preparing the Analysis of the Hardware Benchmark Test Results

Do the following on the machine on which the analysis is to be performed:

1. Open the QVD Generator.qvw file in QlikView Desktop and reload the data.

2. Open the HWBM-Analyser.qvw file in QlikView Desktop and reload the data.

https://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQwhttps://qliktechnologies365.sharepoint.com/:f:/s/ScalabilityLab/Eodm95Sn7K5PsXFG-iZjQF0BhO1eM59v9LW2W4EPc92cQw


Submitting the Hardware Benchmark Test Results for Review

Note: Your test results may contain personal data. If you choose to send the test results to the Qlik

Scalability Center, any personal data within the test results shall become available to Qlik. You

agree you have the permission from any data subjects whom the data may be about to send the

personal data to Qlik. Any personal data received by the Qlik Scalability Center will be treated in

accordance with the Qlik Cookie & Privacy Policy.

If you wish to submit your HW BM test results to the Qlik Scalability Center for review, upload the

results directory of the HW BM package to the testresults folder on the Scalability Center FTP site.

The same files should be included as are needed when analyzing the results yourself.

It is recommended to use an FTP client with SSL support when uploading your files. If you do not

have access to an FTP client, you can access the FTP site at: https://ftpeu.qliktech.com/thinclient/

FTP account details:

• FTP site (requires a secure SSL connection): ftpeu.qliktech.com

• User: SC-files

• Password: Files4Benchmarking

As a final step, send an email to [email protected] to notify the Qlik Scalability Center that

new files have been uploaded for review.

https://www.qlik.com/us/legal/cookies-and-privacy-policyhttps://ftpeu.qliktech.com/thinclient/

Qlik Sense Hardware Benchmark

© 2020 QlikTech International AB. All rights reserved. Qlik®, Qlik Sense®, QlikView®, QlikTech®, Qlik Cloud®, Qlik DataMarket®, Qlik Analytics Platform®, Qlik NPrinting®, Qlik Connectors®,

Qlik GeoAnalytics®, Qlik Core®, Associative Difference®, Lead with Data™, Qlik Data Catalyst®, Qlik Associative Big Data Index™, Qlik Insight Bot™ and the QlikTech logos are trademarks

of QlikTech International AB that, where indicated by an “®”, have been registered in one or more countries. “Attunity” and the Attunity logo are trademarks of Attunity Ltd. Other marks and

logos mentioned herein are trademarks or registered trademarks of their respective owners.

About Qlik

Qlik is on a mission to create a data-literate world, where everyone can use data to solve their most

challenging problems. Only Qlik’s end-to-end data management and analytics platform brings together

all of an organization’s data from any source, enabling people at any skill level to use their curiosity to

uncover new insights. Companies use Qlik products to see more deeply into customer behavior,

reinvent business processes, discover new revenue streams, and balance risk and reward. Qlik does

business in more than 100 countries and serves over 48,000 customers around the world.

qlik.com