Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
We are finding slowness in accessing Qlik cloud from Africa while the same applications work fast from UAE.
The client has found certain requests while by using fiddler and asking for further details on these requests.
Could someone please assist me with what these requests stand for and if any of these can be disabled to make the access faster.
thanks,
Florence
Hi @Flosom
It looks like your network requests are for our client managed product rather than for Qlik Cloud, which is our SaaS product (one indicator is that your requests call api/v1/streams, which don't exist in Qlik Cloud).
There are a large number of factors in client managed deployments which can cause slowness, usually originating from an organisation's network and VPN - are there elements there you could review rather than trying to cut things out of the hub? My concern is that if you block certain elements, we cannot guarantee that the hub will work correctly, and future upgrades may become quite difficult.
Hey @Flosom
If you look at the time it takes to load each asset, they are roughly proportional to the size of the file, so it's probably just a slow network. Bundling the files together would be unlikely to help a great deal since the same volume of data still needs to go over the network.
However - it could be useful to verify that the environment is operating as expected. There's a good video which runs through a series of concepts and tools that you can use to do this here.
You could also verify network speed by putting a 10MB file (or larger) into a content library on the Qlik Sense server and provide that URL to the client. They can then share how long it takes to load that content, which you can compare with a direct connection to determine whether it's simply a bandwidth problem.
Hi @Flosom
It looks like your network requests are for our client managed product rather than for Qlik Cloud, which is our SaaS product (one indicator is that your requests call api/v1/streams, which don't exist in Qlik Cloud).
There are a large number of factors in client managed deployments which can cause slowness, usually originating from an organisation's network and VPN - are there elements there you could review rather than trying to cut things out of the hub? My concern is that if you block certain elements, we cannot guarantee that the hub will work correctly, and future upgrades may become quite difficult.
Hi @DaveChannon ,
A big thank you for reply as we are struggling to make the customer understand the effect of network factors affecting the slowness. We have simultaneously requested network ping & latency details from the client.
We have also got the below list of .js & .css requests which they believe to be causing slowness. Could you shed some light on the requests. We have the client asking if we could move all the files to a single folder so that it can be accessed easily, instead of requests to search many folders & subfolders.
request you to shed some light on the same.
thanks,
Florence
Hey @Flosom
If you look at the time it takes to load each asset, they are roughly proportional to the size of the file, so it's probably just a slow network. Bundling the files together would be unlikely to help a great deal since the same volume of data still needs to go over the network.
However - it could be useful to verify that the environment is operating as expected. There's a good video which runs through a series of concepts and tools that you can use to do this here.
You could also verify network speed by putting a 10MB file (or larger) into a content library on the Qlik Sense server and provide that URL to the client. They can then share how long it takes to load that content, which you can compare with a direct connection to determine whether it's simply a bandwidth problem.