<?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 Re: Qliview app performance in conditional display in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Qliview-app-performance-in-conditional-display/m-p/436597#M1160534</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Update: See attached document for QVW optimization techniques&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;QlikView tends to calculate charts only when they are active (maximized or restored from the minimized state). In the case of multiple charts spread on different sheets, calculations on a chart/sheet tend to begin only when the sheet is activated. This means, calculations will &lt;STRONG&gt;not&lt;/STRONG&gt; take as much memory when a chart or sheet is not active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This applies to regular charts (read: chartts without conditional display). Fortunately, this also seems to be the case with charts that are conditionally displayed.&amp;nbsp; When a chart is set to calculate on a specified 'Calculation Condition', calculations only begin with the calculation criteria is met. This apparently results in better application performance, and is in fact, one of the tricks, to optimize application in the case of large data sets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a gist, you are indirectly optimizing the performance of the application by letting it to compute charts only when they are active (visible, in your case).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have worked with quite large data sets in the recent past and have implemented something similar with positive results, and your results shouldn't be any different &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Khaled.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 20 Jan 2013 07:43:16 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-01-20T07:43:16Z</dc:date>
    <item>
      <title>Qliview app performance in conditional display</title>
      <link>https://community.qlik.com/t5/QlikView/Qliview-app-performance-in-conditional-display/m-p/436596#M1160532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;My qlikview application has a large number of charts (straight and pivot tables) that are displayed conditionally.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does putting the condition in the 'Calculation condition' or the 'show condition' mean that the chart will be loaded only&amp;nbsp; if the condition is satisfied.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does that improve application performance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jan 2013 06:39:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qliview-app-performance-in-conditional-display/m-p/436596#M1160532</guid>
      <dc:creator>sonikajain</dc:creator>
      <dc:date>2013-01-20T06:39:14Z</dc:date>
    </item>
    <item>
      <title>Re: Qliview app performance in conditional display</title>
      <link>https://community.qlik.com/t5/QlikView/Qliview-app-performance-in-conditional-display/m-p/436597#M1160534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Update: See attached document for QVW optimization techniques&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;QlikView tends to calculate charts only when they are active (maximized or restored from the minimized state). In the case of multiple charts spread on different sheets, calculations on a chart/sheet tend to begin only when the sheet is activated. This means, calculations will &lt;STRONG&gt;not&lt;/STRONG&gt; take as much memory when a chart or sheet is not active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This applies to regular charts (read: chartts without conditional display). Fortunately, this also seems to be the case with charts that are conditionally displayed.&amp;nbsp; When a chart is set to calculate on a specified 'Calculation Condition', calculations only begin with the calculation criteria is met. This apparently results in better application performance, and is in fact, one of the tricks, to optimize application in the case of large data sets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a gist, you are indirectly optimizing the performance of the application by letting it to compute charts only when they are active (visible, in your case).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have worked with quite large data sets in the recent past and have implemented something similar with positive results, and your results shouldn't be any different &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Khaled.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Jan 2013 07:43:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Qliview-app-performance-in-conditional-display/m-p/436597#M1160534</guid>
      <dc:creator />
      <dc:date>2013-01-20T07:43:16Z</dc:date>
    </item>
  </channel>
</rss>

