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.
Deprecation notice: At the end of 2022 this tool will cease to receive updates. The tool will continue to get updates to support performance testing of Sense releases during 2022, after this only the Qlik Sense Enterprise Scalability Tools will receive updates.
Supported versions of Qlik Sense: all 2020, all 2021, 2022-feb
Included parts are:
Standalone application for creating and executing a simulation script
(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.
I suspect your simulation-machine and Qlik Sense-machine have different time zone settings in Windows or the machine names does not match.
Different time zone settings will put the test and the performance counters in different time zones and the alignment does not meet the criteria of the where-clause. Note the where-clause is using a key that both include the timeslot and the machinename.
Having this alignment problem will cause problems when analyzing. Make sure all machines are synchronized in time and time zone and re-run the tests.
PCDummy is a field in a staging table used for concatenating all found performance counter qvd's.
The reason for the where-clause is so analysis over long periods of time, with Performance Counters for the full time frame, can be performed without loading millions of rows. It is there to ensure alignment and lower the data volume but if you are careful when analyzing then you can still use the data.
Currently these qvw's do not support or handle Performance Counters and Qlik Sense Scalbility Tool simulations to be logged in different time zones.
If your problem is the machine name, then you will need to use the TestLogMeta-file to connect the simulation to the Performance Counters. A simulation normally use full domain name and Performance Counters use the Windows Machine name. This is step #5 in the Quick Start on page 1 and in more details on page 4 of the "User Guide for SC Result Analyzer.pdf".
Note: Using windows built-in unzip functionality will not allow the .exe to launch unless unblocking zipped package first (properties -> unblock).
When downloading any zip file from the internet windows will unfortunately block it as a "security" measure. If the the zip file is not unlocked prior to unzipping the exe-file will be blocked from executing producing an error as the one you describe. Unblocking the zip file or unzipping it with a third party tool such as 7-zip (http://www.7-zip.org/a/7z1507-x64.exe) should solve the problem for you.