Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Posting on Qlik Community is temporarily paused for some users. Thank you for patience and we'll update you soon!
cancel
Showing results for 
Search instead for 
Did you mean: 
korsikov
Partner - Specialist III
Partner - Specialist III

Best settings QS server for slow client (GPRS)

I did some research using the developer console in chrome.

The result - at a rate of Regular 2G (250 kb/s 300ms   ) and disabled the cache page does not load.

I do not have time to load client.js  and  have error

Uncaught Error: Load timeout for modules: assets/hub/hub

http://requirejs.org/docs/errors.html#timeout

also noted that this error occurs when the total page load timing  exceeds 100000 ms, although in the proxy settings specify the parameters keep-alive timeout (sec) 300.

the file Client.js size is different for different versions of the server. In Version 2.0.4 is 3.0 mb. in Version 2.1.1  - 4.1 Mb

where I dig further to find an answer? how to provide customers with access to such a small connection speed?

1 Solution

Accepted Solutions
korsikov
Partner - Specialist III
Partner - Specialist III
Author

i'm found. require.js Default value  WainSecond = 100

change hub.html

<script>require.config( { baseUrl: "../resources", urlArgs: "?1441973317977", waitSeconds: 300 } )( ["assets/client/client"] );</script>

and tested.

but one thing is driving me crazy.I change the files, but when I load a Web page, they contain old information. Already overloaded server completely and not just service.

View solution in original post

2 Replies
korsikov
Partner - Specialist III
Partner - Specialist III
Author

i'm found. require.js Default value  WainSecond = 100

change hub.html

<script>require.config( { baseUrl: "../resources", urlArgs: "?1441973317977", waitSeconds: 300 } )( ["assets/client/client"] );</script>

and tested.

but one thing is driving me crazy.I change the files, but when I load a Web page, they contain old information. Already overloaded server completely and not just service.

korsikov
Partner - Specialist III
Partner - Specialist III
Author

then one of two things. Either the server keeps a web page in memory, or somewhere in the browser saved the old version of the web page