Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Apr 26, 2022 5:53:32 AM
Mar 19, 2013 12:26:27 PM
Memory usage of the QlikView Server Service continues to increase as the server is being utilized. Not all RAM is being released as expected, even as no users are active on the server and documents are unloaded from memory.
This is working as expected!
QlikView’s memory usage can be broken up into two main categories:
Necessary memory
This consists out of internal data structures, each document’s database, definition of GUI, every user’s session state etc. This will be unloaded from memory when the document timeout is reached.
Note that document timeout does not start to count until all sessions against it is closed
Cache
Results of calculations previously carried out to avoid recalculating. This memory can theoretically be lost and recalculated each time, but it will not be released once the document timeout is reached. Instead, QlikView will use the Working Set Limit defined to manage memory usage.
Working Set Limit:
By default, each QlikView Server is set to a Low Working Set Limit of 70% and a High limit of 90%. The QlikView Server Service will try to use physical memory exclusively and not use the Page File at all up until the Low value is reached.
Once the Low value is reached, QlikView will begin discarding old cache data and replace it with new where possible. QlikView will also signal Windows that it can begin using the page file if necessary. When the High working set limit is reached, QlikView will try to stop caching data altogether. Note that at this point issues with the services will begin to arise (performance/stability problems). The QlikView Event log will usually shed light on that and help identify whether or not you might require more memory or not.
QIX Engine Memory Management and CPU Utilization
QlikView and Qlik Sense resource usage and the Qlik Associative Engine Memory Management and CPU Uti...