FAQ

Frequenty Asked Questions

What is the difference between "Base RAM Footprint" and "Committed RAM Footprint"?

Base RAM Footprint is the initial RAM space for storing the application in RAM (data model + UI). This amount is stored once per app, per server, that is hosting an active app. Committed RAM includes the Base RAM Footprint + additional RAM used for the caching of result sets. This RAM number will increase throughout the day until it hits Working Set Minimum, at which time “housekeeping” is done to remove old result sets to clear room for more caching of new result sets and more frequently used result sets.

"Available memory for caching" – when its negative what does it means?

This happens when a chunk of RAM is needed and the server is already close to the Working Set Minimum. Qlik Sense allows the RAM to temporarily go above Working Set Minimum to get more RAM (usually for opening of an app that isn’t already in RAM), then shortly after, performs more housekeeping to bring the RAM back down to Working Set Min. During that window of time, we show the over allocation of RAM as a negative amount available.

The Hourly Breakdown is totally red for Cache RAM and Expensive Objects. Which the insight we should take from here?

None. This sheet will be deprecated in newer versions of this dashboard. Is was based on assumptions that are not accounted for with larger deployments. You are free to keep the sheet and make it work for you, but it was an attempt at pre-set “thresholds” and doesn’t always work.