<?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: Performance Impact of Set Analysis vs Calculated Dimension in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517570#M36972</link>
    <description>Between the two, I would say Set analysis is always a better option.</description>
    <pubDate>Thu, 06 Dec 2018 18:28:05 GMT</pubDate>
    <dc:creator>sunny_talwar</dc:creator>
    <dc:date>2018-12-06T18:28:05Z</dc:date>
    <item>
      <title>Performance Impact of Set Analysis vs Calculated Dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517554#M36952</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a line chart with Dimension&amp;nbsp;&lt;/P&gt;&lt;P&gt;If(Date &amp;gt; '7/15/2018',Date)&lt;/P&gt;&lt;P&gt;and measure Sum(Sales)&lt;/P&gt;&lt;P&gt;I am wondering what is more optimal performance wise using my calculated dimension or using set analysis&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sum({&amp;lt;[Date] = {'&amp;gt;7/15/2018'}&amp;gt;}Sales)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know the best thing to do would be create a flag in my script for Date &amp;gt; 7/15 and use that in my Set Analysis but its not always feasible to have so many flags.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 07:06:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517554#M36952</guid>
      <dc:creator>m_perreault</dc:creator>
      <dc:date>2024-11-16T07:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Impact of Set Analysis vs Calculated Dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517566#M36953</link>
      <description>Set analysis is vast majority of times always faster than if statements.&lt;BR /&gt;the reason is that your if statement gets calculated for each line which means it doesn't get cached.&lt;BR /&gt;while set analysis gets calculated once.&lt;BR /&gt;&lt;BR /&gt;Possible exceptions are really complex aggr within the set.&lt;BR /&gt;Fastest ofcourse is flags. but as you say not always possible and not the most flexible</description>
      <pubDate>Thu, 06 Dec 2018 18:18:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517566#M36953</guid>
      <dc:creator>dplr-rn</dc:creator>
      <dc:date>2018-12-06T18:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Impact of Set Analysis vs Calculated Dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517570#M36972</link>
      <description>Between the two, I would say Set analysis is always a better option.</description>
      <pubDate>Thu, 06 Dec 2018 18:28:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517570#M36972</guid>
      <dc:creator>sunny_talwar</dc:creator>
      <dc:date>2018-12-06T18:28:05Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Impact of Set Analysis vs Calculated Dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517576#M36977</link>
      <description>&lt;P&gt;Thank you for your response.&amp;nbsp; Could you explain further what you mean by&lt;/P&gt;&lt;P&gt;'&lt;SPAN&gt;the reason is that your if statement gets calculated for each line which means it doesn't get cached.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;while set analysis gets calculated once.'&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Dec 2018 18:36:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517576#M36977</guid>
      <dc:creator>m_perreault</dc:creator>
      <dc:date>2018-12-06T18:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Impact of Set Analysis vs Calculated Dimension</title>
      <link>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517592#M36978</link>
      <description>simply put it goes through each line of the data to evaluate your if condition.&lt;BR /&gt;while set analysis evaluates the set once per visualization (then again when filters are applied)&lt;BR /&gt;&lt;BR /&gt;check these&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Why-is-it-called-Set-Analysis/ba-p/1468208" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Why-is-it-called-Set-Analysis/ba-p/1468208&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Set-Analysis/ba-p/1468344" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Set-Analysis/ba-p/1468344&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Dec 2018 19:05:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Performance-Impact-of-Set-Analysis-vs-Calculated-Dimension/m-p/1517592#M36978</guid>
      <dc:creator>dplr-rn</dc:creator>
      <dc:date>2018-12-06T19:05:31Z</dc:date>
    </item>
  </channel>
</rss>

