Max RAM usage 79 GB when the Physical RAM of Server is 64 GB, Please explain

[shyamcharan]

Hi Experts,

We have the production server with actual RAM of 64 GB.

However, the governance dashboard shows the Maximum RAM usage as 79 GB on a day and for an hour.

Could someone please explain what this means?

Thanks in advance.

[Sonja_Bauernfeind]

Hello!

In summary, what likely happened was that more memory was needed than physically available and QlikView was utilizing virtual memory (so including the page file). 

If you're curious on how our engine handles memory, I'd recommend reading the material available in QIX engine memory management and CPU utilization (kb 000034822). We also have a video with more details and focused on QlikView available in QlikView Memory Management (000025040). 

Kind Regards, 

Sonja 

[shyamcharan]

Hi Sonja,

Thank you heaps for your response. That clarifies my question.

Could you also please advise on how the QlikView Publisher utilizes the RAM.

Any documentation link you have to support ? Thanks heaps in advance.

[Sonja_Bauernfeind]

Hello, @shyamcharan !

The Publisher uses the same engine, though it is designed differently and doesn't keep information in cache or documents loaded. It loads the document it is supposed to work with in, does its reload/distribution/etc, and then the document gets removed from memory again.

If you are looking for information on how to scale the Publisher, see Scaling the QlikView Publisher. 

Don't forget to mark an answer that you found here as a solution to your question to help other community members find what helped you 🙂

[Brett_Bleess]

Just one more point of clarification regarding Publisher and memory usage, unlike QlikView Server, the Publisher can make use of Disk Page File, there is no requirement that things reside in physical memory, but as you know, OS swapping to disk is going to pretty much kill the server, so you want to do your best to be sure Publisher is using physical memory.  If QlikView Server and Publisher are running on the same server, you may need to adjust your Low Working Set limit in the QlikView Server Performance tab settings to a lower value to allow the OS to get more memory back from QlikView Server to allocate to Publisher...  Hopefully this in addition to what Sonja has provided is what you need, shout if you have further questions and as Sonja noted, do not forget to use the Accept as Solution button on any post(s) that helped you with your questions.

Regards,
Brett