Skip to main content

Scalability

Announcements
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
samppppp
Partner - Explorer II
Partner - Explorer II

Analyzing Qlik Scalability Tools results

Hi,
Considering there is a lot of information out there, I am a little bit confused as to what to do with the resulting files after executing scenarios with Qlik Scalability Tools. I have read about QSSTAnalyzer, SCResultAnalyzer and QSAEAnalyzer, but I am still unsure about any of them. We have setup QSSTAnalyzer, however most sheets end up empty except Simulation Data and ServerMeasures.
We are trying to find the CPU/RAM usage, and much more informations, of Qlik Sense applications after executing scenarios with Qlik Scalability Tools.

Looking forward to pointers regarding which Analyzer app to use.
Thanks!

1 Solution

Accepted Solutions
Sebastian_Fredenberg

Hi, 

SCResultAnalyzer lets you analyze Qlikview or Sense tests, while the QSSTAnalyzer allow you to analyze tests made towards Sense using Qlik Sense Scalability Tools or Qlik Sense Enterprise Scalability tools. In other words you have the correct analyzer.

First make sure that you put the files in the correct folders in the folderstructure. The test files should be in Exerciser,Gopherciser or Jmeterlogs (depending on tool used). You seem to have that correct so next up is to make sure that the performance counter file is in the Serverlog folder.

If all that is correct but you can't see CPU/RAM, try and change the following drop downs on the ReadMe tab in the Analyzer:

PC Level: Detail
PC Timeframe: Full

Regards

View solution in original post

2 Replies
Sebastian_Fredenberg

Hi, 

SCResultAnalyzer lets you analyze Qlikview or Sense tests, while the QSSTAnalyzer allow you to analyze tests made towards Sense using Qlik Sense Scalability Tools or Qlik Sense Enterprise Scalability tools. In other words you have the correct analyzer.

First make sure that you put the files in the correct folders in the folderstructure. The test files should be in Exerciser,Gopherciser or Jmeterlogs (depending on tool used). You seem to have that correct so next up is to make sure that the performance counter file is in the Serverlog folder.

If all that is correct but you can't see CPU/RAM, try and change the following drop downs on the ReadMe tab in the Analyzer:

PC Level: Detail
PC Timeframe: Full

Regards

bergerlu
Partner - Contributor
Partner - Contributor

Is the QSSTAnalyzer compatible with Qlik Sense June 2018 ?