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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
jpjust
Specialist
Specialist

Windows diagnosed a low virtual memory condition - Microsoft-Windows-Resource-Exhaustion-Detector

Hi,

In one of our qliksense server, we see the following error:

Event Description:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Engine.exe (10928) consumed 11720503296 bytes, nlparser_r.exe (1020) consumed 1560207360 bytes, and Repository.exe (8108) consumed 518823936 bytes.

Any idea on where exactly to and see the cause for this low virtual memory condition?

Any experience on this issue will be appreciated.

Thanks

11 Replies
Maria_Halley
Support
Support

 

This can be normal QlikSense behavior.

QlikSense is an in memory application and it does consume a lot of RAM.

When you open an app on the server it gets loaded to RAM. The app seizes in RAM in not the same as on disk. It can be many times bigger in memory.

A 1 GB app could be 5-10 in RAM (or more), it depends on the data model and design of the document.

Once the apps are loaded it stays in memory until the app timeout has passed (default 8h). The appt timeout does not start to count down until all sessions against it is closed.

It is normal that the memory consumption stays high even if no one is logged in.

We also cache calculations and session information.  This does not get cleared when the app gets unloaded but stays in memory until the working set limit is reached.

Then we start to clear it out, started with the data that was used the longest ago.
 

Maria_Halley
Support
Support

@jpjust

 

In addition to my above answer, I also would suggest these Videos, made by Qlik Experts on the subject.

 

https://www.youtube.com/watch?v=GF07UnSQKKo&t=1525s

https://www.youtube.com/watch?v=2UgctHdHLTI&t=191s