Qlik Sense Enterprise Scalability Tools

[Daniel_Larsson]

This tool is being deprecated, updates will be received during 2026, but thenceforth be considered deprecated.

The Qlik Sense Enterprise Scalability Tools (QSEST) are used to create and run load and performance tests towards Qlik Sense Enterprise on Windows (QSEoW).

Included parts are:

• Documentation on how to use the package
• Command line tool for Windows, Mac and Linux. This command line tool (gopherciser) is open source and can be found here .
• GUI for Windows and Linux.

Downloadable files can be found here:
📎 Qlik Sense Enterprise Scalability Tools 

Qlik Sense documents to help analyze result and log files can be found here :https://community.qlik.com/docs/DOC-15451

Change log

v1.14.1

• Bugfix for entering JWT key path
• Gopherciser v0.21.23 -> v0.22.2
  • Avoid errors with JWT keys when running as wasm in GUI
  • improved IPv6 handling

  • bugfixes

v1.14.0

• Added linux arm64 binaries
• Removed osx binaries
• Updated scheduler including support for linux arm64
• Support for QSEoW Nov 2025
• Gopherciser v0.20.1 -> v0.21.23
  • Bugfixes
  • Support nl insights objects
  • Support Treedata calculation condition
  • Add sn-nav-menu to supported objects.
  • Add arm64 linux binaries
  • Add scheduler and CPU metrics to prometheus pushed metrics
  • Add configurable thinktime inbetween publishing and unpublishing sheets
  • Add optional timeout settings to open app action
  • Add possibility to generate empty script to template command
  • Autodetect privatekey type and update default signing algorithm when using jwtsettings
  • Support for PS256,PS384,PS512,ES256,ES384,ES512 and EdDSA JWT signing algorithms
  • Duplicatesheet improvements
  • Limit request concurrency while getting app structure
    

v1.13.0

• Gopherciser v0.18.7 -> v0.20.1
  • QSEoW Nov24 support
  • Support sn-tabbed-container object
  • Openapp changed for Nov24 api compliance
  • New default websocket reconnect backoff pattern
  • Bugfixes

v1.12.0

• Updated scheduler
• Gopherciser v0.18.5 - v0.18.7
  • performance enhancements
  • new action stepdimension

•  

Your use of Qlik Sense Enterprise Scalability Tools 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 Enterprise Scalability Tools, however please check QlikCommunity for additional information on use of these products.

[Santos_M]

Hi, I'm facing the same issue... Since we upgraded to May 2025 we are getting this error with scalability tools. Did you find any fix for this? It was working before...

Thanks in advance.

[Daniel_Larsson]

Hi, 

The tool was re-tested towards towards patch 10 and things ran correctly including connect functionality. Can you create a scenario with only a openhub action, 1 user and 1iteration towards the server and see if reported error gives additional clues?

[Santos_M]

Hi,

Thanks for you answer! We actually did that... We tested last Friday before our upgrade with a certain scenario, after upgrading to May 2025 patch 9 the same test started to fail with following error:

It gets even worse unfortunately... Pushing the "Connect" button works fine and shows "Connection successfull", however when I select "Connect & populate app structures" I get this error already.

I didn't notice anything related to this error in the release notes of patch 10, so not sure it would fix the issue...

Can you confirm that patch 10 fixes this issue?

Thanks in advance!

[Daniel_Larsson]

Hi, 
no cannot confirm that since we have not been able to reproduce the issue, and don't have a patch 8 or 9 to test against currently. I can only say we tested patch 10 successfully, with connect, connect and get appstructure and running actual load scripts. 403 indicates something with authentication though. I assume running a script with 1 iteration 1 user and only openhub gets the same 403 errors? 
Which form of authentication is used? static headers?

[jbaechle]

When attempting to enter text in the JWT key path input field using the latest version (1.14.0) for Windows, the following error is raised:  'error reading private key from file: open <path>: not implemented on js'. 

[Daniel_Larsson]

---

@jbaechle wrote:

When attempting to enter text in the JWT key path input field using the latest version (1.14.0) for Windows, the following error is raised:  'error reading private key from file: open <path>: not implemented on js'. 

---

Hi, I can confirm getting this issue, will see if I can get a fix for it. Does using v1.13.0 work for your use case meanwhile?

[jbaechle]

Yes, it does.  Thanks.

[Daniel_Larsson]

---

@jbaechle wrote:

When attempting to enter text in the JWT key path input field using the latest version (1.14.0) for Windows, the following error is raised:  'error reading private key from file: open <path>: not implemented on js'. 

---

v1.14.1 should now have this fixed.