<?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 Memory limitation in Server in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192760#M1323713</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;We are having some performance issues that prevent us to work with QV docs efficiently.&lt;/DIV&gt;&lt;DIV&gt;Below is our scenario.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Our qv users have some qv objects that consume very high amount of memory.&lt;/DIV&gt;&lt;DIV&gt;As soon as such an object is clicked to maximize, memory usage starts to increase rapidly.(See attached Task Manager screenshot)&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;We are aware of that we need to refine these kind of objects for fine-tuning. But, until this workshop, we need to prevent undesirable memory consumption.&lt;/DIV&gt;&lt;DIV&gt;We want to display "Out of memory" error on charts to our users so that we will know which objects causing extra-mem consumption.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;We know that there are several options to limit memory both in Document and Server side.&lt;/DIV&gt;&lt;DIV&gt;After some investigations, Memory tab in chart objects can do the trick. (see attached Memory window screenshot).&lt;/DIV&gt;&lt;DIV&gt;But we figured out that this limitation only works if we access to document directly (File - Open). (See attached Out of Memory error screenshot)&lt;/DIV&gt;&lt;DIV&gt;If we open the document in Server (File - Open in Server), the memory usage again starts to increase. (See attached Task Manager screenshot)&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The question is&lt;/DIV&gt;&lt;DIV&gt;How we REALLY limit memory usage of objects?. Could you please suggest a working and proven way of memory limitation.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1283_sourceID:1283" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1284_sourceID:1284" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1285_sourceID:1285" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
    <dc:creator>niceqlik</dc:creator>
    <dc:date>2026-01-26T18:19:17Z</dc:date>
    <item>
      <title>Memory limitation in Server</title>
      <link>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192760#M1323713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV&gt;We are having some performance issues that prevent us to work with QV docs efficiently.&lt;/DIV&gt;&lt;DIV&gt;Below is our scenario.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Our qv users have some qv objects that consume very high amount of memory.&lt;/DIV&gt;&lt;DIV&gt;As soon as such an object is clicked to maximize, memory usage starts to increase rapidly.(See attached Task Manager screenshot)&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;We are aware of that we need to refine these kind of objects for fine-tuning. But, until this workshop, we need to prevent undesirable memory consumption.&lt;/DIV&gt;&lt;DIV&gt;We want to display "Out of memory" error on charts to our users so that we will know which objects causing extra-mem consumption.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;We know that there are several options to limit memory both in Document and Server side.&lt;/DIV&gt;&lt;DIV&gt;After some investigations, Memory tab in chart objects can do the trick. (see attached Memory window screenshot).&lt;/DIV&gt;&lt;DIV&gt;But we figured out that this limitation only works if we access to document directly (File - Open). (See attached Out of Memory error screenshot)&lt;/DIV&gt;&lt;DIV&gt;If we open the document in Server (File - Open in Server), the memory usage again starts to increase. (See attached Task Manager screenshot)&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;The question is&lt;/DIV&gt;&lt;DIV&gt;How we REALLY limit memory usage of objects?. Could you please suggest a working and proven way of memory limitation.&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1283_sourceID:1283" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1284_sourceID:1284" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;IMG alt="error loading image" class="jive-image error-loading-image" src="https://community.qlik.com/legacyfs/online/-1285_sourceID:1285" /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192760#M1323713</guid>
      <dc:creator>niceqlik</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Memory limitation in Server</title>
      <link>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192761#M1323715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a similar issue before - our qvw was 7GB (400 millions records) and we only have 28GB of memory to use.&lt;/P&gt;&lt;P&gt;No matter we play around with the memory - it keep give the user out of memory. We normalized the data and remove any possible syntetic key issue. Then finally we change the coding as well.&lt;/P&gt;&lt;P&gt;The code that the problem before :&lt;/P&gt;&lt;P&gt;=if (Age='18-49, sum (18cost) ,sum(50 cost))&lt;/P&gt;&lt;P&gt;what the solution is put the sum outside the if: sum(if )(age='18-49',18cost,50cost)&lt;/P&gt;&lt;P&gt;this reduce the calculation at the record level which create the memory issue. The guy in the forum help us and pointed the issue - any agregate function have to be outside to reduce the calculation.&lt;/P&gt;&lt;P&gt;That my 2 cents&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Senjaya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Mar 2010 14:59:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192761#M1323715</guid>
      <dc:creator />
      <dc:date>2010-03-23T14:59:32Z</dc:date>
    </item>
    <item>
      <title>Memory limitation in Server</title>
      <link>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192762#M1323717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, I understand that these kind of situation can be solved by refining expressions .&lt;/P&gt;&lt;P&gt;But it is not what i'm looking so far.&lt;/P&gt;&lt;P&gt;I just want to limit memory usage of Qv objects and display "Out of Memory" error on charts when users open docs in Server. There is an option in Chart Properties - &amp;gt; General - &amp;gt; Memory.&lt;/P&gt;&lt;P&gt;But this option is only functioning when directly opening Docs using (File - Open)&lt;/P&gt;&lt;P&gt;How can we make use of this option in Open In Server mode.?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Mar 2010 15:35:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Memory-limitation-in-Server/m-p/192762#M1323717</guid>
      <dc:creator>niceqlik</dc:creator>
      <dc:date>2010-03-23T15:35:50Z</dc:date>
    </item>
  </channel>
</rss>

