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.
Greetings All,
I'm working to setup QS Scalability Tool v3.0 on a client server and having trouble authenticating via the "header" virtual proxy I've setup (see screenshot below) according to the Marcus Spitzmiller video. Does anyone have any experience trying to connect to Qlik using the Virtual Proxy "Header" Authentication method? Appreciate any thoughts/comments etc.. Thanks!
Lou Zunin wrote:
Greetings All,
I'm working to setup QS Scalability Tool v3.0 on a client server and having trouble authenticating via the "header" virtual proxy I've setup (see screenshot below) according to the Marcus Spitzmiller video. Does anyone have any experience trying to connect to Qlik using the Virtual Proxy "Header" Authentication method? Appreciate any thoughts/comments etc.. Thanks!
To be able to log in as a header user you need to have the header name you created attached to your requests. This can be achieved in multiple ways. For your case and testing logging in as a header user, which I agree is a good thing to always try to do before testing, I would recommend using firefox and the modify headers plugin (Modify Headers), the plugins for chrome that I tried don't properly add the headers to websockets. Fiddler could also be used for the same thing.
Hi,
I am experiencing a similar problem that other users have reported in the comments section. I get the error as "Failed to connect to app".
I am using a header auth and HTTPS.
I have exported and imported the certificates as suggested in the documentation.
I am able to connect to my server with mozilla + modify headers. But, I still get the certificate error and i have to add an exception to browse the app in mozilla.
When i connect to the same app with header auth in the scalability tool, HeaderName and VirtualProxyPrefix is updated properly and the app name and server is also updated. For server i am providing only the IP address as i am not able to connect to that server with the server name.
Could you please help me understand what am i missing here to establish a connection to the app.
Thanks,
Aadil
Aadil M wrote:
...
But, I still get the certificate error and i have to add an exception to browse the app in mozilla.
...
Thanks,
Aadil
Hi,
This part is likely your problem. The client still isn't trusting the certificate and thus the sdkexerciser will not trust it causing the connection to fail.
Make sure you establish the connection using the the domain name specified in the certificate (normally the FQD).
Hi, Daniel, I'm facing a weird issue. I'm not able to connect to the app even when I know my virtualproxy parameters are correct (I know it cause I can access to the app via browser using the virtualProxy). I've read all the comments here and already checked everything (blocking zip, same QS version, header parameters, etc.) and have no idea what's going on.
On the other side I've tried to do it on the Desktop version (3.0) and can't connect to the app either, but there I have one final doubt (on the VirtualProxyPrefix option what should I put? anything? "default" (think is anything as I remeber to read on the documentation but not sure about it)
Any ideas of what could be the cause?
Cheers,
Andrés
Got it on the desktop!! Had to include the .qvf at the end of the App parameter. I'm going to try to use the JSON generated on the desktop to used on the server as far as I'm still uncapable of connect to the app from there.
Cheers,
Andrés
Andres P wrote:
Hi, Daniel, I'm facing a weird issue. I'm not able to connect to the app even when I know my virtualproxy parameters are correct (I know it cause I can access to the app via browser using the virtualProxy). I've read all the comments here and already checked everything (blocking zip, same QS version, header parameters, etc.) and have no idea what's going on.
Have you tried using firefox with the ModifyHeaders plugin, using the same settings, i.e. adding a header with your headername and user, using the prefix in the url and using http or https same as with tool. Also, are you using https? When connecting with firefox does it prompt you to add an exception?
On the other side I've tried to do it on the Desktop version (3.0) and can't connect to the app either, but there I have one final doubt (on the VirtualProxyPrefix option what should I put? anything? "default" (think is anything as I remeber to read on the documentation but not sure about it)
When connecting to Desktop:
Hi Daniel, thanks for the fast reply. I've already made it works! Your comments were useful, thanks.
Cheers,
Andrés
I'm trying to create a scenario that maxes out the CPU. Here are some questions I have.
Thanks in advance!
Hi Micah!
What are you interested in finding out in your test? If you want to create a boundary test where you see how many users it will take to saturate the CPU on your server using the specific scenario, a good idea is to run indefinite iterations and a linear ramp-up with a high number of concurrent users and see how long it takes to saturate the system.
The arrival pattern feature is useful in determining system behavior under realistic circumstances but not really for boundary testing. The concurrent user value here will act as a governing limit, whereas the actual amount of users will be determined by the arrival pattern parameters. To help you with this, there is a Sense app called "Arrival Pattern Helper.qvf" included in the tool, under the ArrivalPatternTools folder.
I hope this satisfies your question!
Sebastian