Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More

How to time a Qlik Sense Websocket connection

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Chris_Rice
Former Employee
Former Employee

How to time a Qlik Sense Websocket connection

Last Update:

Mar 4, 2022 10:09:37 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 14, 2017 7:00:39 AM

Using Dev Tools in your browser of choice it’s possible to get more precise timing of your websocket connections. This can be helpful in troubleshooting apps that are slow or timing out.

Here are a few steps to follow:

In this example, we will use the Chrome Dev Tools. Press CTRL + Shift + I to get it to open. It should look like this:

Developer Tools in Chrome.png

With the Network tab selected, proceed to open your application:
 
Chrome Developer Tools Network tab load in seconds.png
 
We’re interested in that top line with the Type of websocket, select that:
 
Developer Tools in Chrome request is not finishe dyet.png
 
On this timing tab, we can see how long it took to establish a connection to the app. This includes authentication, authorization, and loading the app into memory (if not accomplished previously).
 
If we want to break that down further, we can go to the Frames tab:
 
Developer Tools in Chrome handle id.png

Here we can see the length of the individual frames as well as the time in which they were loaded.  This should give you a good idea of how long each frame took based on the load time of the previous frame.  Furthermore, the green frames are those sent to the server while the white handles are the responses.  You can compare them by matching the Handle number with the ID in the response as highlighted.
 

Environment:

Labels (2)
Contributors
Version history
Last update:
‎2022-03-04 10:09 AM
Updated by: