Qlik Sense Scalability Tools

[Daniel_Larsson]

This package (referred to as Qlik Sense Scalability Tools) contains a complete set of tools for easy creation, execution and analysis of load/performance tests.

This tool is now deprecated and will not receive any further updates, please use the Qlik Sense Enterprise Scalability Tools instead.

Supported versions of Qlik Sense: all 2020, all 2021, 2022-aug

Included parts are:

• Standalone application for creating and executing a simulation script
• Documentation on how to use the package
• Regression analyzer
• Benchmarking package
• App evaluator package

QlikView and Qlik Sense documents to help analyze result and log files (previously included in this package) can be found here :https://community.qlik.com/docs/DOC-15451

Troubleshooting

For help to troubleshoot connection problems, please review Appendix A of the documentation or Connection Troubleshooting Tips

Change log

v5.17.0

• Add support for Qlik Sense May 2022 release
• Add support for Qlik Sense Aug 2022 release
  

v5.16.0

• Add support for Qlik Sense Feb 2022 release
  

v5.15.0

•  Add support for Qlik Sense Nov 2021 release

v5.14.0

• Add support for Qlik Sense Aug 2021 release

(See Readme.txt for changes in earlier versions of the tool.)

Your use of Qlik Sense Scalability Tool will be subject to the same license agreement between you and Qlik for your Qlik Sense License. Qlik does not provide maintenance and support services for the Qlik Sense Scalability Tool, however please check QlikCommunity for additional information on use of these products.

[mountaindude]

Good thinking - but it was manually unblocked before extracted.

Re object ids, is it the qId of for example a list box (in which I want to make a selection) that should be used?

[mountaindude]

Possible it is related to crappy data in repository?

There are various error messages about this in the logs...

We're considering running the repository cleanup scripts, but they are really scary too - end users can after all access the production applications right now, we don't want to break that..

[mountaindude]

Hmm, manually retrieving the IDs does not work either.

It's the ID in red that should be used, right?

Then, the script looks like this:

This gives the following result when executed:

Starting test towards Uri: ws://senselab2eu.qlik2.local/loadtest

12:56:16 Workers:0 Errors:0 Warnings:0 Requests:0

12:56:18 1-1  Object reference not set to an instance of an object.

Test Execution Finished.

WarningCount: 0

ErrorCount: 1

Finishing writing logs...

I.e. looks like it connects to the server just fine, but don't find the list box it should make selections in.

Which is kind of in line with not being able to get app structure - if it cannot open the app, it of course won't get a reference to the listbox within the app...

Removing the Select action gives us this:

Starting test towards Uri: ws://senselab2eu.qlik2.local/loadtest

12:58:09 Workers:1 Errors:0 Warnings:0 Requests:0

Test Execution Finished.

WarningCount: 0

ErrorCount: 0

Finishing writing logs...

Which is kind of weird... How can it clear selections in an app, if it in the next step fails to access objects in the app?

Strange.

[Daniel_Larsson]

The id in read is the id for the filterpane, i.e. the id for the container. The id next to the search button is the id for the listbox, so this is the id you want to use instead.

From the execution output you will not see much for such a short scenario. If you check the logs inside the Results forlder you should see that OpenHub and OpenApp actions succeeded successfully. I cannot fully figure out why connecting during execution works, but "connect to app" doesn't work. The only major difference is interprocess communication through a named pipe in the connect to app case.

Btw, the clearall action will not do anything if there is nothing in current selections.

[mountaindude]

Ah, got the IDs mixed up - thanks.

Still failing though. I'll see if I can put a trace or Wireshark or something on it...

[evanchang11]

Hi All,

I'm having difficulty to execute to the scalability tools for Qlik Sense

the version is ScalabilityTools-v0.3.0.18 and my OS version Windows 10 Pro.

possible due to compatibility?

[SebastianFabian]

Did you unblock the zip file before unzipping? (See the original post)

[mountaindude]

This is strange. Still  can't get the tool (version v0.3.0.18, running on rim node of Sense 3.0.1 cluster) to connect to an app and get its structure... Very frustrating.

[mountaindude]

Daniel, is there a way to generate the app structure via a command line call to some app?

[Daniel_Larsson]

Göran Sander wrote:

Daniel, is there a way to generate the app structure via a command line call to some app?

Hi,

Yes there's a way to do it from commandline, it's not very straightforward though. This will work for the current version of the tool (v.0.3.0.18) and might get removed or changed in the future.

First we need to create a json file doing what we want.

So start with making a copy of the json script where you have the settings for the app/server you want to connect to. Edit the script in a texteditor and make the following changes:

1. Find the entry "Worker": "ScenarioWorker" and change it to "Worker": "GetAppStructureWorker"

2. Add a CustomConfig section containing a filepath parameter with the name of the file to be created (containing the app structure

So e.g. the changed part of the file could look like this

{

..... Other stuff

  "worker" : "GetAppStructureWorker",

  "CustomConfig" : {

    "filepath" : "MyAppStructure.json"

  }

.... Other stuff

}

When you have the script, let's say you name it getappstructure.json, Open a command window and go to the appropiate sdkexerciser subfolder for the sense version you're using.  E.g.

{quote}cd ToolRoot\SDKExerciser\v3.0

{quote}

Then to execute, assuming the script is in the same folder

SDKExerciserConsole.exe config=getappstructure.json

If connection works, it should now create a file called MyAppStructure.json (or whatever you named it to) which can be read into the gui with the "app structure from file" function.