I'm facing an issue lately with my QV server deployment.
recently, users tend to get very often an error message saying the server is unreachable (and they can't open documents via access point).
exploring that issue led me to the conclusion is high RAM usage which is solved only by restarting the Qlikview server service.
what I've noticed is that users which opens documents increase (as expected) the RAM usage, BUT when they close the documents the RAM they used is NOT releasing... the RAM usage only keeps increasing and increasing until users can no longer open documents until a restart is being made.
which explains that this is how QV originally designed to work (use every available RAM for better end-user experience) but what if that RAM usage effects badly on other users?
it doesn't seem right to schedule a service restart few times a day...
To decrease the timeout-settings will help to minimize the risks of running out of memory but then it could happens that the user-experience isn't like before if documents must be loaded into the RAM instead of using the cached document.
I think you should take a look on the QlikView Governance Dashboard to evaluate the min/avg/max RAM consumption over the last month to get a real foundation to decide how much should be the working set settings be and/or to increase the RAM and/or to optimize the tasks and applications.
Infra team added more RAM to the machine (144GB instead of 80GB) as a temporary solution (the current resource was NOT enough obviously).
so far so good, but we need to figure out the proper solution which will be either improving documents, splitting documents, adding a new Server just for users and the current will remain for QVS tasks or upgrading to Sense.
timeout of document doesn't help. i've tried to play and adjust the Min/Max working set which helped also (changed from 50/65 to 70/80-85).
