Since last week we switched over to a brand new Qlikview environment. Our setup include Qlikview Enterprise Server 11.2 SR4 on top of Windows Server 2012, Intel Xeon with 24 cores 128GB RAM.
In our old env. we had an average of 16GB RAM commited from the the 24GB. In the new env. it starts with 16GB but climbs steadily to 91GB(!). If you restart the qvs service it does go back to 16 but climbs back again to it's "comfort zone".
I know Qlikview "loves" memory and this behavior is partly by design but it seems to me unacceptable to restart the server every second day.
I'm sure you are aware this is normal QVS behaviour. QVS will take advantage of caching and it helps the users who login to access the application by positive performance. QVS will do caching until it reaches the Low and the High Set limit. (By default 70% and 90%). The purpose of having hardware resources is to take advantage and QVS does the same. However, it should delete the cache after reaching the threshold which is 90% by default. And generally Server becomes very slow when it reaches the limit and sometimes it will crash and only way to restore the system is by restarting the Server.
If you are having this issue where RAM is not being released then please check the below settings:
1. Allow Only One Copy of Document in Memory (This should be enabled because if you are creating multiple versions of the same document then it will hurt your Ram Usage).
2. Check if there is any Virus scan on the mounted folder and if possible raise an exception for this folder.
3. Use Windows PerfMon and check for the peaks by using Memory, Processor and Cache groups. Add the relevant counters and do some baby sitting with the Server to understand which document/ App is causing the issue.
Also; if the working set limits (70/90) is hit, QVS will only flush parts of the cache to get the memory usage below the limit that triggered the purge, not removing all cache for that document.