<?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: Set analysis performance in Nov 2018 in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1545197#M39286</link>
    <description>&lt;P&gt;We are running into a similar issue going from Feb 2018 to Nov 2018.&amp;nbsp; For some strange reason rebuilding the table in the new version seemed to help.&amp;nbsp; I have no idea why.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Feb 2019 16:24:34 GMT</pubDate>
    <dc:creator>bbergstrom</dc:creator>
    <dc:date>2019-02-15T16:24:34Z</dc:date>
    <item>
      <title>Set analysis performance in Nov 2018</title>
      <link>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1538154#M38835</link>
      <description>&lt;P&gt;We are currently testing the November 2018 upgrade in our development environment and have found a significant difference in performance with set analysis. We use a lot of tables to display transaction level data in our apps, with set analysis used to perform calculations etc.&lt;/P&gt;&lt;P&gt;We are upgrading from the June 2018 version and comparing the same app we are able to load a table with 90k+ records and ~50 columns, but in the Nov 2018 version the same table can on display &amp;lt;20k records before we get an error saying "out of calculation memory".&lt;/P&gt;&lt;P&gt;Straight tables in general are taking longer to load. Is anyone else experiencing the same issues?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sharon&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 06:42:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1538154#M38835</guid>
      <dc:creator>s-puddle</dc:creator>
      <dc:date>2024-11-16T06:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: Set analysis performance in Nov 2018</title>
      <link>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1545197#M39286</link>
      <description>&lt;P&gt;We are running into a similar issue going from Feb 2018 to Nov 2018.&amp;nbsp; For some strange reason rebuilding the table in the new version seemed to help.&amp;nbsp; I have no idea why.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2019 16:24:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1545197#M39286</guid>
      <dc:creator>bbergstrom</dc:creator>
      <dc:date>2019-02-15T16:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: Set analysis performance in Nov 2018</title>
      <link>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1545341#M39292</link>
      <description>Ok thanks will see if that works</description>
      <pubDate>Sat, 16 Feb 2019 00:23:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Set-analysis-performance-in-Nov-2018/m-p/1545341#M39292</guid>
      <dc:creator>s-puddle</dc:creator>
      <dc:date>2019-02-16T00:23:13Z</dc:date>
    </item>
  </channel>
</rss>

