Qlik Community

Scalability

Announcements
June 28, 10AM ET: Qlik Nation and Qlik Community present: CyberSleuth REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
Daniel_Larsson
Employee
Employee

Qlik Sense Scalability Tools

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
  • 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.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.

Labels (2)
192 Replies
korsikov
Partner
Partner

help me, please.

i'm read manual for QC RA

2. Copy needed log files from their original places and put them into the correct locations under
the <Test Root> folder structure.

we have:

Archived Logs = c:\ProgramData\Qlik\Sense\Repository\Archived Logs\

EventLogs = ???

ServerLogs ==??

SessionLogs = ?? maybe 'c:\ProgramData\Qlik\Sense\Log\Engine\QS_Session_Engine.txt'


lse
Employee
Employee

Hi, Alexander.

The folder structure, used for this tool, is the same as the QlikView Scalability Tool. Tests performed with both tools could be analyzed with the same version of the QVD Generator and Analyzer.

The EventLogs and SessionLogs folders are reserved for QlikView11-logs so if you are using the Qlik Sense Scalability Tool then you do not have files to put in these folders.

ServerLogs are for Performance Counters generated with Windows PerfMon and the xml-template provided with the tools.

/lars

korsikov
Partner
Partner

more question

QS_Result_demo not load data from PerformanceCounterQVD.

I believe because of unknown value, PCDummy,  which is loaded as empty

exapmple

PerformanceCounters:

LOAD * Inline [PCDummy];

FOR EACH File IN FILELIST ('QVD\PerformanceCounterQVD\*.qvd')

  //Performance counters linked with TimeSlot ONLY. Used for Calendar time analysis

  Concatenate (PerformanceCounters)

  LOAD

  *,

  ProcessName & '@' & ServerName AS ProcessServer

  Where Exists(%KEY_MachineTimeSlot);

  LOAD

      ServerTimeStamp,

      ServerFileName,

      ServerName & '-' & KEY_TimeSlot & '-' AS %KEY_MachineTimeSlot,

      ServerData,

      ServerName,

      Replace(Replace(ProcessName, 'PROCESS(', ''), ')', '') AS ProcessName,

//     TextBetween(ProcessName, '(', ')') AS ProcessName,

      ProcessDimension,

      CoresCalc AS Cores

  FROM

  '$(File)' (QVD)

// Where

// (

// ProcessDimension = 'Private Bytes' or

// ProcessDimension='Working Set' or

// ProcessDimension='% Processor Time' or

// ProcessDimension='% Privileged Time'

// )

// and

// (

// ProcessName='PROCESS(ENGINE)' or

// ProcessName='PROCESS(PROXY)' or

// ProcessName='PROCESS(REPOSITORY)' or

// ProcessName='PROCESS(SCHEDULER)' or

// ProcessName='PROCESS(QVS)' or

// ProcessName='PROCESS(_TOTAL)' or

// ProcessName='PROCESS(IDLE)' or

// ProcessName='PROCESS(QVWEBSERVER)' or

// SubStringCount(ProcessName, 'W3W')>0 or

// SubStringCount(ProcessName, 'POSTGRES')>0

// )

  ;

NEXT File

DROP Field PCDummy from PerformanceCounters;

If I comment out the condition of the data is fully loaded. Show me my mistake

PerformanceCounters:

LOAD * Inline [PCDummy];

FOR EACH File IN FILELIST ('QVD\PerformanceCounterQVD\*.qvd')

  //Performance counters linked with TimeSlot ONLY. Used for Calendar time analysis

Concatenate (PerformanceCounters)

LOAD

*,

ProcessName & '@' & ServerName AS ProcessServer

// Where Exists(%KEY_MachineTimeSlot);

  LOAD

      ServerTimeStamp,

      ServerFileName,

      ServerName & '-' & KEY_TimeSlot & '-' AS %KEY_MachineTimeSlot,

      ServerData,

      ServerName,

      Replace(Replace(ProcessName, 'PROCESS(', ''), ')', '') AS ProcessName,

//     TextBetween(ProcessName, '(', ')') AS ProcessName,

      ProcessDimension,

      CoresCalc AS Cores

  FROM

  '$(File)' (QVD)

  ;

NEXT File

//DROP Field PCDummy from PerformanceCounters;

lse
Employee
Employee

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".

br

/lars

korsikov
Partner
Partner

Thanks for the tip.

I originally suggested that the reason in a different host name in the logs

For hostname QSDEMO in the settings file have the same name, but the logs are fully qualified domain name of the connection qsdemo.myhost.com

time zone a same in all hosts. All hosts is part one windows domain.

Not applicable

Hi Daniel,


I download this tool and trying to install, but it is not installing and generating an error "Qlik Scalability Tool has stopped working".

Is there any specific steps needs to be follow before installing the tool ? I'm using Qlik Sense 2.1 version and windows 7 64-bit OS.

Daniel_Larsson
Employee
Employee
Author

Did you follow the note  above?

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.

Not applicable

Thank you Daniel, it worked !

Not applicable

thanks for sharing