Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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:
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
v5.16.0
v5.15.0
v5.14.0
(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.
Dear dlo,
The link provided for '200M-PTSalesAnalytics.qvf' in 'Qlik Sense Hardware Benchmark' manual is not working. Is there an alternative location where we can download the file?
Thanks in advance for any answer.
Kind regards,
ilias
Hi Ilias,
It should be available again.
Best regards,
Frederic
I am using v5.3.0 with Sense Enterprise Feb19.
I have 3 scenarios that work fine when executed by themselves. They basically just load 3 different demo apps whose only purpose is to generate some load on the servers.
But when I create a schedule and add those 3 scenarios, the schedule refuse to work. All steps fail. No log files are written to the ./Results folder, but the ./Logs folder gets a new log file "TestScheduler-[7552]_20190424195915.log":
Date Timestamp Thread Level Logger Message Exception 2019-04-24 19:59:15,662 165 1 INFO TestScheduler.Program Running test schedule at C:\plabs_apps\scalabilitytools-5.3.0\Schedules\Full cluster load test.json 2019-04-24 19:59:15,693 196 1 INFO TestScheduler.Program Notification pipe token is 0632f281-becc-486c-9f06-aebbf7aca13b 2019-04-24 19:59:15,704 208 1 INFO TestScheduler.Program Command pipe token is 0fcb6848-a2db-46bd-a8ac-98b2f00f7c94 2019-04-24 19:59:15,711 214 1 INFO TestScheduler.Program Create subfolder is set to True 2019-04-24 19:59:31,227 15731 6 INFO TestScheduler.Tasks.SDKExerciserTask Invoking SDKExerciserConsole: C:\plabs_apps\scalabilitytools-5.3.0\SDKExerciser\v3.2\SDKExerciserConsole.exe config="C:\plabs_apps\scalabilitytools-5.3.0\Scenario\MeetupCom.json" configname="1-Meetup-DEV1-MeetupCom" server=192.168.100.30 app="2a9b3ffc-a022-49c2-83be-a64cb8b670f8" ssl=True headername=X-Qlik-User virtualproxyprefix=hdrdev1 iterations=30 usernameprefix=Exerciser concurrentusers=3 rampupdelay=20.00 executiontime=-1 instancenumber=1 appmode=Open newuserforeachiteration=True afteriterationwait=ConstantWait afteriterationwaittime=60 logDir="C:\plabs_apps\scalabilitytools-5.3.0\Results\Full cluster load test 190424 075916" 2019-04-24 19:59:31,240 15744 6 ERROR TestScheduler.Tasks.SDKExerciserTask Error while running task "1 - Meetup-DEV1" System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at TestScheduler.Tasks.SDKExerciserTask.RunSDKExerciserTask(IEventAggregator eventAggregator, CancellationToken cancellationToken) in C:\Jws\workspace\scalabilitytools\TestScheduler\TestScheduler\Tasks\SDKExerciserTask.cs:line 96 2019-04-24 19:59:46,201 30705 6 INFO TestScheduler.Tasks.SDKExerciserTask Invoking SDKExerciserConsole: C:\plabs_apps\scalabilitytools-5.3.0\SDKExerciser\v3.2\SDKExerciserConsole.exe config="C:\plabs_apps\scalabilitytools-5.3.0\Scenario\LA-parking-tickets.json" configname="2-LA-parking-tickets-DEV2-LA-parking-tickets" server=192.168.100.30 app="12dab8b9-f654-4c30-bed9-22cf97c13053" ssl=True headername=X-Qlik-User virtualproxyprefix=hdrdev2 iterations=30 usernameprefix=Exerciser concurrentusers=3 rampupdelay=20.00 executiontime=-1 instancenumber=1 appmode=Open newuserforeachiteration=True afteriterationwait=ConstantWait afteriterationwaittime=60 logDir="C:\plabs_apps\scalabilitytools-5.3.0\Results\Full cluster load test 190424 075916" 2019-04-24 19:59:46,211 30715 6 ERROR TestScheduler.Tasks.SDKExerciserTask Error while running task "2 - LA-parking-tickets-DEV2" System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at TestScheduler.Tasks.SDKExerciserTask.RunSDKExerciserTask(IEventAggregator eventAggregator, CancellationToken cancellationToken) in C:\Jws\workspace\scalabilitytools\TestScheduler\TestScheduler\Tasks\SDKExerciserTask.cs:line 96 2019-04-24 20:00:01,201 45705 6 INFO TestScheduler.Tasks.SDKExerciserTask Invoking SDKExerciserConsole: C:\plabs_apps\scalabilitytools-5.3.0\SDKExerciser\v3.2\SDKExerciserConsole.exe config="C:\plabs_apps\scalabilitytools-5.3.0\Scenario\kickstarter.json" configname="3-Kickstarter-QA1-kickstarter" server=192.168.100.30 app="e5c416f7-9e75-40e9-a40a-ed8a95889052" ssl=True headername=X-Qlik-User virtualproxyprefix=hdrqa1 iterations=30 usernameprefix=Exerciser concurrentusers=3 rampupdelay=30.00 executiontime=-1 instancenumber=1 appmode=Open newuserforeachiteration=True afteriterationwait=ConstantWait afteriterationwaittime=60 logDir="C:\plabs_apps\scalabilitytools-5.3.0\Results\Full cluster load test 190424 075916" 2019-04-24 20:00:01,212 45716 6 ERROR TestScheduler.Tasks.SDKExerciserTask Error while running task "3 - Kickstarter-QA1" System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start() at TestScheduler.Tasks.SDKExerciserTask.RunSDKExerciserTask(IEventAggregator eventAggregator, CancellationToken cancellationToken) in C:\Jws\workspace\scalabilitytools\TestScheduler\TestScheduler\Tasks\SDKExerciserTask.cs:line 96 2019-04-24 20:00:04,226 48730 1 INFO TestScheduler.Program Shutting down
It talks about "The system cannot find the file specified", and indeed the file "C:\plabs_apps\scalabilitytools-5.3.0\SDKExerciser\v3.2\SDKExerciserConsole.exe" does not exist. Seems the schedule executor is looking for a SDKExerciser that doesn't exist...
Bug or feature?
I know I've pinged the Scalability Devs about this, but I'm pretty sure this is the issue that I ran into. The cause for me was this element:
This is where you'd specify a SDK version. It isn't required by the UI and, if left blank, will default to calling the 3.2 version which doesn't exist in modern versions of the tool.
If I understand, your problem is that the tasks are not starting as expected. Correct? What is listed in the "Prerequisites" column? This is what determines what triggers the start of the tasks. In my example, task 2 is configured to start when task 1 is finished.
It can be configured by selecting a task, clicking Edit and going to the Triggers tab.