QV Scalability Tools (QV10,QV11,QV12)

[Daniel_Larsson]

This package (referred to as QVScalabilityTools) contains a complete set of tools for easy creation, execution and analyzing of load/performance tests and regression tests.

QlikView documents to help analyze result and log files(This was previously included in this package):Scalability Results Analyzer

Older versions of the tool can be found here: Tool for easy creation of load/performance tests of QlikView (v.10 and 11)

Tools for Qlik Sense can be found here: Qlik Sense Scalability Tools

Note: Using windows built-in unzip functionality will not allow the .exe to launch unless unblocking zipped package first (properties -> unblock).

Note: Regarding Apache Log4j, reference CVE-2021-44228 (also referred to as Log4Shell), these set of tools are not directly vulnerable to the exploit, however JMeter, the tool required as a separate download, is. How to mitigate the vulnerability for JMeter has been documented here : https://community.qlik.com/t5/Knowledge/Qlik-Scalability-tools-and-log4j/ta-p/1872009 

Included parts are:

• Standalone application for creating a JMeter script
• Support files for launching the script by utilizing the JMeter engine (JMeter installed is a pre-requisite)
• Documentation on how to use the package

Version 1.2.7->1.2.8

• Changes Section Access requests

Changelog 1.2.6->1.2.7

• NTLM support removed due current solution broken and lack of a new secure solution.
• Small updates for static content, for future product releases.

2019-08-26

Documentation updates due to:
- New recommended JMeter version (4.0)
- Changes to the licensing for the Oracle Java implementation (seehttps://www.oracle.com/technetwork/java/javase/overview/oracle-jdk-faqs.html)
- Open-source Java Development Kits (JDKs) have been verified for use with JMeter and the QlikView Scalability Tools

Changelog 1.2.5->1.2.6

• Added support for QlikView 12.50 and 12.20SR10

Changelog 1.2.4->1.2.5

• Added support for QlikView 12.30

Changelog 1.2.3->1.2.4

• Added support for JMeter 4.0 and Java 9.
• Bugfixes for regression testing
• Added actions: Select Excluded, Select All, Select Possible
• Added support for 12.20 SR3

Changelog 1.2.2->1.2.3

• Bugfix for export to excel action
• Added transfer state (bookmark) support for document chaining
• GUI: Template selection more accurately show supported Qv versions

Changelog 1.2.1->1.2.2

• Bugfixes, make sure minimum amount of selections are respected in certain corner cases

Changelog 1.2->1.2.1

• Improved performance for high throughput scenarios

Changelog 1.1 -> 1.2

• Improved assertions logic to show faulty actions as errors
• Change JMeter template scripts to use groovy instead of beanshell
• New prerequisites:
  • JMeter version 3.0
  • Java 64-bit JRE 8

Your use of QVScalabilityTools will be subject to the same license agreement between you and QlikTech for QlikView Server. QlikTech does not provide maintenance and support services for QVScalabilityTools, however please check QlikCommunity for additional information on use of these products.

PLEASE NOTE:

The supported versions of Java are 8 and 9. Supported version of JMeter are 3.0 and 4.0, but not 3.2

[Daniel_Larsson]

The easiest way to test if everything works ok is to run a small scenario using 1 user and 1 iteration and see that you don't get any errors.

[9717023463]

Hi,

I have made the connection and set the settings as per the document in qlikview scalability tool.

But as soon as I run the script I get errors in it. The error %tage is around 80%.

The error which it shows is [Full(GC System)][PS Young Gen].........[GC(Allocation Failture)].

Please find the attached image of the error.

[PawelF]

Hi Shashank,

We need some information, in order to help you.

1. what Java version are you using? You can check this from command line typing java -version

2. Have you changed the default Heap Size for Java in the tool settings?

3. How much memory does the machine from which you're trying to run test have?

Kind regards,

[9717023463]

Hi Pawel,

Thanks for your reply.

Firstly I am using java  version 8(latest one).

Yes, I have changed the default heap size from 512 to 3072.

It has 8 GB RAM.

[PawelF]

Hi,

1. Is it 64-bit version of Java?

2. Where have you changed the heap size? The latest version of the tools have 3072MB by default.

3. 8GB should be enough memory to run tests.

So the main suspect right now is Java.

[9717023463]

Hi,

Yes it is a 64 bit version of java. Please find the attached image of it.

The heap size is 3072 by default in tool .

The application which we are testing is very small.

[9717023463]

Hi,

One more thing when I run it in CMD i get a warning namely Java Hotspot<TM> 64 bit server VM warning : Ignoring option MaxPermSize=64M; Support was removed in 8.0  .

Please find the attached image also.

[PawelF]

Hi Shashank,

Thanks for the information.

The part about ignoring MaxPermSize can be ignored, it is a setting no longer used by JVM and this is not connected to the errors during execution.

The problem based on the previous information seems to be connected to Garbage Collections (GC), this is something we have not seen before.

If you run a very short version of the test (i.e. like 5 minutes), could you provide the jmeter.log file after the test was run? Maybe it will contain some information we can use to investigate this.

If you have not changed the logging options in the tool the jmeter.log should be located in JMeter/bin folder.

Kind regards,

[9717023463]

Hi,

Please find the attached jmeter log file from the below link.

jmeter - Google Drive

[PawelF]

It seems like it might be something related to JMeter version and Tool version.

Just to make sure - are you using the latest version of the QV Scalability Tools?

Also you're using JMeter 3.2, right?