This download contains a document that outlines all required information on how to access/execute/analyze/submit results for the QlikView Hardware Benchmarking test package. The goal with the QV HW Benchmarking package is to have a unified QlikView specific Hardware test that can be executed for various environments with the aim to establish a matrix for comparisons on how different servers and configurations perform with QlikView. The document contains information on how to download additional files needed and where to upload the results. This package only supports QlikView 11.
The QV Hardware benchmarking package consists of two parts, stand-alone QV desktop based and a QlikView Server based Benchmark tests, focusing different areas of hardware performance. QV documents and scripted tests are part of the Benchmarking package.
This package can be used for analytics on your own to perform comparisons of performance for different hardware configurations, but more important is that any test results are provided to the Scalability Center, making sure that your results becomes part of the general summary to improve coverage and statistical accuracy of the results.
Please take the time to help out with these types of activities to establish useful guidelines about which servers to recommend (i.e. where QlikView performs well).
Changes for version 3.4
Changes for version 3.3
Changes for version 3.2.1
Changes for version 3.2.0
Changes for version 3.1:
Major changes for version 3.0:
We got some reports about problems with QVScalabilityTools and QlikView Hardware Benchmarking test when used with JMeter 3.2. We recommend using JMeter 3.0 or 4.0.
do the following:
in the execution tab right click on the scenario and select open in jmeter
when jmeter opens, right click on view results tree and select enable
then press CTRL+R to run. you will see in the results tree what step is causing the errors.
The application contains an embedded license up to 1000 Document CALs, so you should not use any of your own platform. The document describes how to set it up so you don't have to allocate any additional CALs from the server that hosts this QVW.
Remove the following line from each file in the BenchmarkJMX folder to correct the problem.
<CookieManager guiclass="CookiePanel" testclass="CookieManager" testname="HTTP Cookie Manager" enabled="true">
<collectionProp name="CookieManager.cookies" />