topic Scalability Results Analyzer in Scalability

Scalability Results Analyzer

Yang_Jiao — Mon, 04 Jan 2021 16:12:10 GMT

QSSTAnalyzer.zip

This package contains a Qlik Sense app, which can be used for analyzing Qlik Sense performance test results generated by the Qlik Sense Scalability Tools‌ and the Qlik Sense Enterprise Scalability Tools.

Included parts:

QSSTAnalyzer.qvf
GopherciserTest: A test results folder
FolderTemplate.zip: A template of folder structure

SCResultAnalyzer.zip

This package (referred to as SC Results Analyzer) contains a set of QlikView documents, which can be used for analyzing both QlikView and Qlik Sense performance test results generated by the Qlik Sense Scalability Tools‌ and the QV Scalability Tools.

Included parts:

QVD Generator.qvw
ServerMetaFetcher.qvw
SC_Results - DemoTest.qvw: An analyzer for test results
DemoTest: A Demo test results folder
FolderTemplate.zip: A template of folder structure

------------------------------------------------------------------------------------------------------------------------------------------

Update 2021-01-04:

Bugfix for missing DataFiles connector

Update 2020-12-18:

Bugfix for session counts

Update 2019-11-14:

Added default values and "only one selected" for key visualization dimensions in the QSSTAnalyzer app

Update 2019-10-31:

Added API fields
Added "Gopherciser, Metric" sheet for API data analysis

Update 2019-10-14:

New QSSTAnalyzer user interface
Improved QSSTAnalyzer capabilities
Added support for using QSSTAnalyzer in Qlik Sense Enterprise on Cloud Services (QCS)

Update 2019-05-17:

New version of QSSTAnalyzer with added support for data from Qlik Sense Enterprise Scalability Tools
Added sample data from Qlik Sense Enterprise Scalability Tools

Update 2017-09-26:

New version of the SCResultAnalyzer updated for the QV12 Hardware Benchmark Package

Update 2017-03-17:

Added QSSTAnalyzer

Your use of Scalability Tools will be subject to the same license agreement between you and Qlik. Qlik does not provide maintenance or support services for the SC Result Analyzer and QSSTAnalyzer, however please check Qlik community for additional information on its use.

Re: Scalability Results Analyzer

Anonymous — Wed, 24 Feb 2016 21:51:10 GMT

I wanted to propose additional graphs for analyzing results

(Chart below makes sense for testing a single document.)

And response times by test case

and number of concurrent sessions with test duration:

Re: Scalability Results Analyzer

Anonymous — Mon, 10 Oct 2016 13:03:48 GMT

dlo‌

We made some changes to the SC_Results script in order to properly link the data:

/****** LINKTABLE **********/

Original:

TestMachine & '-' & %KEY_TimeSlot AS %KEY_MachineTimeSlot

Changed to:

TestMachine & '-' & Timestamp(Left(%KEY_TimeSlot, Len(%KEY_TimeSlot)-1),'YYYY-MM-DD hh:mm') & '-' AS %KEY_MachineTimeSlot

/*****PerformanceCounters********/

Original:

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

Changed to:

ServerName & '-' & Timestamp(KEY_TimeSlot,'YYYY-MM-DD hh:mm') & '-'

AS %KEY_MachineTimeSlot

/*****Events********/

Original:

ServerNameEvent & '-' & %KEY_TimeSlot AS %KEY_MachineTimeSlot

Changed to:

ServerNameEvent & '-' & left(%KEY_TimeSlot,16) & '-' AS %KEY_MachineTimeSlot,

/*****Sessions********/

Original:

ServerNameEvent & '-' & %KEY_TimeSlot AS %KEY_MachineTimeSlot

Changed to:

ServerNameEvent & '-' & left(%KEY_TimeSlot,16) & '-' AS %KEY_MachineTimeSlot,

Any chance you can investigate that and include it in the next release?

Re: Scalability Results Analyzer

Daniel_Larsson — Tue, 11 Oct 2016 09:29:41 GMT

Hi,

Thanks you for your suggestion. Just wondering, under which circumstances is it you get the problem?

Re: Scalability Results Analyzer

Anonymous — Tue, 11 Oct 2016 16:41:59 GMT

Hi Daniel,

I've just reviewed the original code and the issue seems to be somewhere else. I've reverted the changes one by one and commented out only one line in the PerformanceCounters tab:

Where Exists(TimeSlot, PCTimeSlot)

I understand that the line is there to only keep the data that is relevant to the test. The issue I had was that even though TimeSlot and PCTimeSlot looked the same, for some records they were different:

i.e.

2016-09-22 09:56 <>2016-09-22 09:56:00 , but

2016-09-22 09:55 = 2016-09-22 09:55:00

In order to make it work I created two text fields:

Text(Timestamp(KEY_TimeSlot,'YYYY-MM-DD hh:mm'))

as TextPCTimeSlot

in the PerformanceCounters, and

text(Timestamp(Left(JMeter_TimeSlot, Len(JMeter_TimeSlot)-3), 'YYYY-MM-DD hh:mm'))

AS TextTimeSlot

in the Calendar, and apply the where exist on the two text fields:

Where Exists(TextTimeSlot, TextPCTimeSlot).

Re: Scalability Results Analyzer

Miguel_Angel_Baeyens — Wed, 11 Jan 2017 09:50:28 GMT

Running the tool with QV 11-20 SR15, I cannot get info for sessions in the QVS. The expression seems to use fields that are not the the analyzer QVW, such as ActiveUserId, ServiceLogType or ServiceLogName. I'm missing other files? I can see the sessions running the old QVW

Re: Scalability Results Analyzer

Daniel_Larsson — Wed, 11 Jan 2017 14:40:49 GMT

Miguel Baeyens wrote:

Running the tool with QV 11-20 SR15, I cannot get info for sessions in the QVS. The expression seems to use fields that are not the the analyzer QVW, such as ActiveUserId, ServiceLogType or ServiceLogName. I'm missing other files? I can see the sessions running the old QVW

I assume you're taking about the session information in the "Extra" tab. This information comes from the qlikview session log. To see this information you need to

Make sure you get the session log from the server/servers
Make sure you get the log after the sessions has been written to the log. The sessions are not written until either the session times out (by default 30 minutes after last user action) or engine restarts.
Make sure to put the log in the SessionLogs folder for QVD Generation.

In other words you should either wait 30mins after the test (provided default timeout) or restart the qvs before getting the log.

Re: Scalability Results Analyzer

Miguel_Angel_Baeyens — Thu, 12 Jan 2017 13:17:37 GMT

I'm talking about the following objects

Main tab:

Sessions chart

Extra tab:

Session distribution

Sessions and connections

Logs:

Engine, Session

Print Object:

Sessions

As I say in the previous post, I do have the session logs (mostly by restarting the QlikView Server service so the sessions are written) and if I use the old Analyzer.qvw, I can see the sessions. In the newer one, however, the expressions in these charts use fields that are not in the data model, screenshot attached. ServiceLogType, ServiceLogName do not exist in the data model, hence the chart showing nothing.

Re: Scalability Results Analyzer

Daniel_Larsson — Fri, 13 Jan 2017 13:08:15 GMT

The expression you show in the screenshot is for proxy and will only be in the data model if you have a sense log files. For the normal session graph you should see sessions provided your scripts has reached opendoc actions (the session graph counts opendoc for qlikview or openapp for sense). So some questions to verify.

Is it the exact same data you are comparing? (i.e. to be sure you actually see the in the old analyzer)
The QVD's created will differ and can't be reused, did make sure the qvd's was regenerated or deleted before using the new qvdgenerator?
Did you make sure the timezone was set correctly when creating qvd's?

Re: Scalability Results Analyzer

Miguel_Angel_Baeyens — Tue, 17 Jan 2017 12:07:50 GMT

Daniel, I'm copying the logs in two different folders, one where the old QVW Analyzer is, another where the new is. So I reload both QVD Generators, make sure the server names are OK, etc. then load from there to the results. Timezone is the same that the one on my laptop, anyway, I'm loading all logs in the server, so I guess even if it was wrong, since all Jmeter, Scalability Tools and QlikView are on the same server, the time should be the same for all.

What I don't get yet is how the app knows when QlikView or Qlik Sense logs have been loaded, I mean, is there any setting I should change on the QVW itself? There is no Qlik Sense services at all in these servers, only QlikView and all of them running the same version.

I think I can share with you a reduced version (one or two minutes worth of test) and you can tell me what I'm doing wrong

Re: Scalability Results Analyzer

Miguel_Angel_Baeyens — Tue, 17 Jan 2017 12:19:35 GMT

I found it, just needed some time to review the script:

if(substringcount(upper(label),'OPEN DOCUMENT') or SubStringCount(Upper(label), 'OPEN APP')=1,1,0) AS OpenAction,

OPEN DOCUMENT or OPEN APP do not correspond to the labels in the scenarios, therefore those values are never present in the script, therefore the count is actually 0. Changed that to the right label or removing labels in the scenario show values.

So the scenario works, the test works and now the analyzer app works. But if adding values to ACCESSPOINT, or OPEN DOCUMENT or any other action is not recommended or can cause issues because of this, the option should be removed in the GeneratorGui, don't you agree?

Re: Scalability Results Analyzer

Daniel_Larsson — Tue, 17 Jan 2017 14:01:16 GMT

ok now I'm confused, because this doesn't correlate to your previous info:

The old qvd-generator counts the label the same way so you should get exactly the same behavior there if using the same files.
The Extra tab is from Qlikview session logs and shouldn't get affected by this.

Other than that,I agree, if it is not already in documentation that open document label shouldn't be changed it should be added there.

Re: Scalability Results Analyzer

Anonymous — Thu, 09 Feb 2017 04:05:23 GMT

Can someone explain why i am having this error when i try to open the zip file?

Many thanks!

Re: Scalability Results Analyzer

Anonymous — Thu, 09 Feb 2017 05:23:04 GMT

Hi there

Can anyone help me with finding the Performance Counters Logs file? I could not find it in either my local machine or the server. However, i can find the execution log on my local machine.

Many thanks!

Kind regards,

Re: Scalability Results Analyzer

Sebastian_Fredenberg — Thu, 09 Feb 2017 12:49:48 GMT

Hi, could you describe more when you get this error?

Re: Scalability Results Analyzer

Sebastian_Fredenberg — Thu, 09 Feb 2017 13:01:07 GMT

Hello,

The performance counters needs to be set up on the server, according to Appendix A in the Qlik Scalability Tools User Manual. When setting it it up you define where to have the performance counters files saved.

Regards

/sebastian

Re: Scalability Results Analyzer

Anonymous — Tue, 01 Aug 2017 09:16:02 GMT

Hello altogether,

Is it possible to share any document describing each trends of QSSTAnalyzer.qvf?

I would appreciate any comments here.

Thanks and Regards,

Ladislav

Re: Scalability Results Analyzer

dineshmdane — Mon, 13 Nov 2017 11:58:48 GMT

Hi All,

Can anyone explain what is 'success rate per minute' in the analyzer.

Thanks in advance.

Regards,

Dinesh M

Re: Scalability Results Analyzer

agarmanu — Tue, 29 May 2018 15:43:54 GMT

Hi All,

I am able to configure QVD generator and dashboard prior to that i have get all the logs placed and generated the Performance counters as well.

Issue i am getting is sc_results dashboard is not able to show any charts . Do i need to do anything to get the chart works.

Charts which are not working are CPU,CalculationEngine,CPU,Webserver,CPU,Repository, RAM,CalculationEngine, RAM,webserver

Please suggest

Thanks

Re: Scalability Results Analyzer

Sebastian_Fredenberg — Wed, 30 May 2018 07:29:34 GMT

Hi,

If you don't see the Resource utilization (CPU, RAM) it is usually due to 2 reasons:

* The timezone differs between load client and the server, this is changed in the QVD generator

* The name of the server differs in the loadscript and the performance counter files. For example if you connected to an ipadress in the url but the performance counters are stored as the windows machine name. This is changed in the testlogmetafile (edit qvs and webserver settings to match that in the performance counter)

You might need to recreate the QVD:s completely (delete qvd s and redo the generation) after changing the above.

Regards

Sebastian