<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1560663#M13073</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;After our Qlik users have logged out of the Qlik Sense environment, the RAM on the server still stays fairly high. E.g. 40%.&lt;/P&gt;&lt;P&gt;It gives the impression to the user that there is some kind of fault.&lt;/P&gt;&lt;P&gt;However I think this is not true so I try to explain it to them that the 40% is reserved by Qlik services because it is holding on to the app and the cached data about the app so that the next time user opens up a dashboard, they could get a quicker experience because some of the things are already stored in memory. This is why the RAM is "high".&lt;/P&gt;&lt;P&gt;Am I explaining this right? Or if you could tweak my statement to be more correct please do so.&lt;/P&gt;</description>
    <pubDate>Mon, 25 Mar 2019 10:40:42 GMT</pubDate>
    <dc:creator>mwallman</dc:creator>
    <dc:date>2019-03-25T10:40:42Z</dc:date>
    <item>
      <title>Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards</title>
      <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1560663#M13073</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;After our Qlik users have logged out of the Qlik Sense environment, the RAM on the server still stays fairly high. E.g. 40%.&lt;/P&gt;&lt;P&gt;It gives the impression to the user that there is some kind of fault.&lt;/P&gt;&lt;P&gt;However I think this is not true so I try to explain it to them that the 40% is reserved by Qlik services because it is holding on to the app and the cached data about the app so that the next time user opens up a dashboard, they could get a quicker experience because some of the things are already stored in memory. This is why the RAM is "high".&lt;/P&gt;&lt;P&gt;Am I explaining this right? Or if you could tweak my statement to be more correct please do so.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 10:40:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1560663#M13073</guid>
      <dc:creator>mwallman</dc:creator>
      <dc:date>2019-03-25T10:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards</title>
      <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1560725#M13074</link>
      <description>&lt;P&gt;Actually 40% memory usage sounds low! You're server is nowhere near memory starvation.&lt;BR /&gt;In the QMC under Engine/Advanced you have settings for how much memory the Qlik Engine may use.&lt;BR /&gt;Default values here are min 70% and max 90% of internal memory.&lt;BR /&gt;Thus if you have not changed these settings the Qlik Engine has no reason to de-allocate the memory.&lt;BR /&gt;You could lower these limits but why should you?&lt;BR /&gt;Better to supply sufficient RAM to the server and avoid running other systems on the same server.&lt;BR /&gt;Especially if you have a virtual server avoid pooling of resources.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2019 12:14:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1560725#M13074</guid>
      <dc:creator>Anders_Eriksson</dc:creator>
      <dc:date>2019-03-25T12:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards</title>
      <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561305#M13087</link>
      <description>&lt;P&gt;Hi Anders,&lt;/P&gt;&lt;P&gt;So what does it mean the memory usage is low? Yes generally out server doesn't hit the min 70% and 90% max, our QMC settings are with this default.&lt;/P&gt;&lt;P&gt;We do not have high number of apps, 2 at max.&lt;/P&gt;&lt;P&gt;Still I am not sure how to explain why the server holds on to the 40% RAM. Is my explanation in the original thread sufficient?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 12:21:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561305#M13087</guid>
      <dc:creator>mwallman</dc:creator>
      <dc:date>2019-03-26T12:21:25Z</dc:date>
    </item>
    <item>
      <title>Re: Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards</title>
      <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561592#M13090</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/292"&gt;@mwallman&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have a look at the Qlik Support article &lt;A href="https://support.qlik.com/articles/000034822" target="_self"&gt;QIX Engine Memory Management and CPU Utilization&lt;/A&gt; and the associated Qlik whitepaper regarding how Qlik Sense utilizes server resources. Hopefully the article will provide some insight for you.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 20:26:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561592#M13090</guid>
      <dc:creator>Chip_Matejowsky</dc:creator>
      <dc:date>2019-03-26T20:26:34Z</dc:date>
    </item>
    <item>
      <title>Re: Explaining why the RAM stays at a high level after users stop using Qlik Sense dashboards</title>
      <link>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561731#M13094</link>
      <description>&lt;P&gt;It means you don't have any memory issues on the server. Your server is working fine from that information.&lt;BR /&gt;That is under the conditions you are not running virtual memory, not running pooled memory in a virtual server&lt;BR /&gt;and you are not running other software on the same server that requires that memory.&lt;BR /&gt;If you have any of the issues I mentioned forcing Sense to deallocate memory is not the answer.&lt;BR /&gt;The Sense Engine holding on to the memory is per design.&lt;BR /&gt;Applications are held in memory even when not used in order to speed up service of the next user.&lt;BR /&gt;Sense caches applications and search results (states) in memory as long as there is sufficient memory available.&lt;BR /&gt;You can force deallocating by altering those settings but I don't recommend it.&lt;BR /&gt;That would force longer response times as the Engine would be forced to load from disk each time an application is requested.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 08:38:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Explaining-why-the-RAM-stays-at-a-high-level-after-users-stop/m-p/1561731#M13094</guid>
      <dc:creator>Anders_Eriksson</dc:creator>
      <dc:date>2019-03-27T08:38:56Z</dc:date>
    </item>
  </channel>
</rss>

