topic Qlik Scalability tool Taking a long time to execute in Scalability

Qlik Scalability tool Taking a long time to execute

Thu, 15 Dec 2016 23:04:52 GMT

Hello All

i am in process of creating load trest scripts for my company. i have created a 10 step script, 1 user, ntlm authentication

But sometime i am the script is taking a long time to execute completly. i am constantly getting below message in jmeter logs

1481842307706,4,Poll,200,OK,QlikView 1-1,text,true,575,1,1,4

Any help would be appreciated

Re: Qlik Scalability tool Taking a long time to execute

Sebastian_Fredenberg — Fri, 16 Dec 2016 08:06:48 GMT

Hi,

The polling is sent after selection to wait for everything to be calculated on the Engine side. If you constantly get these messages it indicates that either the calculation takes a very long time to perform or that the script gets stuck and never will get the proper response (due to an invalid selection sequence or similar in the script).

To know what is going on I suggest you to first of all check so there is nothing missing in the script (selections in charts existing in containerobjects need the containerid as well for example). Secondly run the script from the jmeter GUI to see at what point the script gets stuck with polling and look into what the request before the poll contains and what the responses from that and the polls are.

To do so, right click on your script in the execution pane and select open in jmeter. Once opened enable the greyed out component "View results tree" and run the script. As the script is running the result tree will allow you to look at all requests ands responses sent when running the script.

Cheers

/sebastian

Re: Qlik Scalability tool Taking a long time to execute

Fri, 16 Dec 2016 15:49:15 GMT

thank you Sebastian

will try that.

wanted to add script is getting stuck with the "poll" log information after a time delay. So i dont think it is the qlikview app.

will this happen if qlikserver kills the session?

I was able to get the script working but had to rewrite it from the point it got stuck.

Not sure if it was some corruption of the file or the qlikserver