<?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 Issue in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Performance-Issue/m-p/1157363#M890085</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume your main-problem is that you used two fact-tables and that quite probably the most of your gui-calculations goes to the fact-table with the consolidated data but your dimension-tables are connected to the detail fact-table. This meant that qlik needs to build huge virtual tables to calculate the expressions. See:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3214"&gt;Logical Inference and Aggregations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3238"&gt;The Calculation Engine&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore I think you will speed up your application if you removed the consolidated table and makes all calculations to the detail fact-table or you concatenate both fact-tables, see: &lt;A href="https://community.qlik.com/qlik-blogpost/2819"&gt;Fact Table with Mixed Granularity&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And further you need to simplify your objects by avoiding calculated dimensions, aggr-functions, nested if-loops, dimension-groups, containers and maybe some more. Furthermore a check if you really need all those fields within your application, see: &lt;A href="https://community.qlik.com/message/1083560"&gt;Document Analyzer V3.0 Update Available&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Aug 2016 13:48:19 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2016-08-23T13:48:19Z</dc:date>
    <item>
      <title>Performance Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue/m-p/1157362#M890084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find attached my data model, and the table statistics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data will be filtered according to access table, for 90% of the users, remaining 10% will have access to the whole content. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The data application is extremely slow, due to the huge amount of data for the 10% of users. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need your guidance to configure a correct machine and make it user-friendly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for your help &lt;/P&gt;&lt;P&gt;Djega&lt;/P&gt;&lt;P&gt;+33(0)0782170324&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue/m-p/1157362#M890084</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Performance-Issue/m-p/1157363#M890085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume your main-problem is that you used two fact-tables and that quite probably the most of your gui-calculations goes to the fact-table with the consolidated data but your dimension-tables are connected to the detail fact-table. This meant that qlik needs to build huge virtual tables to calculate the expressions. See:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3214"&gt;Logical Inference and Aggregations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3238"&gt;The Calculation Engine&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore I think you will speed up your application if you removed the consolidated table and makes all calculations to the detail fact-table or you concatenate both fact-tables, see: &lt;A href="https://community.qlik.com/qlik-blogpost/2819"&gt;Fact Table with Mixed Granularity&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And further you need to simplify your objects by avoiding calculated dimensions, aggr-functions, nested if-loops, dimension-groups, containers and maybe some more. Furthermore a check if you really need all those fields within your application, see: &lt;A href="https://community.qlik.com/message/1083560"&gt;Document Analyzer V3.0 Update Available&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2016 13:48:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Performance-Issue/m-p/1157363#M890085</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-08-23T13:48:19Z</dc:date>
    </item>
  </channel>
</rss>

