Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are experiencing unacceptable long startup times when opening a mashup for the first time. As in the range 5-15 seconds.
To narrow down the scope, we have tried jMeter to test repeatedly downloading the two request taking the most time:
Most requests (50-60%) take less than 100 ms, both require.js and the websocket. Fine.
25% of the requests are in the interval [100 ms, 1000 ms]. Far from great, but ok.
The rest spread out between 1 to 5 seconds. Per request. Some requests taking as long as 10 seconds to complete.
Below is a sample of a test run today. We run 20 iterations, wait a minute, 20 new iterations, etc. (Always waiting 100 ms between each request.)
Y-axis is time of the request, in seconds.
If we zoom in on four of the runs, you better see the spread. There is an indication that the first requests are generally slower than at the end of a test run. But this is not always the case (like test run 3 in the image below).
We cannot find any other pattern correlating to any other known events. Apart from that there seem to be a correlation between the time opening the websocket and the time it takes downloading the require.js.
Does anyone have any ideas on how to divide and conquer this problem?
Do you have any idea how to test if it is: Qlik? NodeJS? The OS? The disk? The VM? The Network?
We are running Qlik Sense and Qlik QAP on Windows 2016 64-bit, 32GB RAM.
It is virtual, but with dedicated memory, disk and CPU.
The test above is removing the mashup and the data model completely from the equation. It is just looking at opening the connection, and getting a fixed file.
What are your response times? Similar?
Any feedback appreciated!
Cheers,
Vegard 🙂
Same issue here with QAP, the app is loaded in 40 -50 seconds and 10 to 15 seconds the browser is waiting idle after a call to a websocket. Once loaded response time of selections is 1 sec or less.
Nicola
Yesterday we did this experiment, when the two virtual machines were both on the same VMhost hardware.
We downloaded require.js, and opened the websocket to the app, using jMeter.
The duration jumps up and down a bit.
If we sort the x-axis by the duration of the test, we get a clearer picture of how many is out of
These tests exclude any client side rendering and JavaScript execution. It tests the server response time only.
We don't know what else is happening on the logical server. But both serveres here are running on the same VM hardware.
Hi Vegard,
really interesting analysis.
Did you find any other detail on this issue and/or contacted the Support?
Cheers,
Riccardo
Hi Riccardo,
We have contacted support, and they have escalated it. But we are still waiting for a meeting with the next people in line.
We have unfortunately not found the cause for this behaviour. Or if anyone else have experienced similar issues.
I have jMeter scripts if anyone are keen to test their own system.
Hi, Vergard,
Maybe you have any kind of solution provided by Qlik Support? We have similar situation and looking for any kind of solutions.
Hi, Vergard,
Maybe you have any kind of solution provided by Qlik Support? We have similar situation too with November 2019 Patch 2.
Best Regards
Francisco