<?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: Dashboard Performance Issue on Access Point in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349268#M414953</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Neha,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be you need to update your QlikView version. I have&amp;nbsp; faced the same issue on one of my client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arvind Patil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Jul 2017 06:41:46 GMT</pubDate>
    <dc:creator>arvind_patil</dc:creator>
    <dc:date>2017-07-21T06:41:46Z</dc:date>
    <item>
      <title>Dashboard Performance Issue on Access Point</title>
      <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349267#M414952</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need your suggestion on best way to worked my access point dashboard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have QV server installed on Windows server 2012R2 with 512GB RAM &amp;amp; 64bit OS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And my application size is 824MB but it's takes time to load data on access point it always buffer after every selection.&lt;/P&gt;&lt;P&gt;So, what should I do to increase my dashboard performance on access point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've done the all optimization techniques to reduce application size but it has heavy calculation of front end which i can't do in back end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Help me for other solution.&lt;/P&gt;&lt;P&gt;Any help will be great appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance.&lt;/P&gt;&lt;P&gt;Neha D.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 06:36:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349267#M414952</guid>
      <dc:creator>neha_shirsath</dc:creator>
      <dc:date>2017-07-21T06:36:30Z</dc:date>
    </item>
    <item>
      <title>Re: Dashboard Performance Issue on Access Point</title>
      <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349268#M414953</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Neha,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;May be you need to update your QlikView version. I have&amp;nbsp; faced the same issue on one of my client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Arvind Patil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 06:41:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349268#M414953</guid>
      <dc:creator>arvind_patil</dc:creator>
      <dc:date>2017-07-21T06:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Dashboard Performance Issue on Access Point</title>
      <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349269#M414954</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you will need to make the heavy calculations lighter by avoiding aggr-functions and nested if-constructs. Quite helpful could be to create flags within the script for the most heaviest calculations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another quite important point is the datamodel itself. If the gui is (too) slow you need to avoid link-table and/or snowflake models and going in the direction of a star-scheme or even a single table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 08:14:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349269#M414954</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2017-07-21T08:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: Dashboard Performance Issue on Access Point</title>
      <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349270#M414955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I have used 2 link table but I cant avoid to used it because scenario like I have multiple dates coming from different table and calendar on multiple dates i.e i have created canonical calendar.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried with flag for heavy calculation but its not affect much in fact nothing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 10:07:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349270#M414955</guid>
      <dc:creator>neha_shirsath</dc:creator>
      <dc:date>2017-07-21T10:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Dashboard Performance Issue on Access Point</title>
      <link>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349271#M414956</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Arvind for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure whether it will solve my issue or not that's why i'm holding this solution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jul 2017 10:09:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Dashboard-Performance-Issue-on-Access-Point/m-p/1349271#M414956</guid>
      <dc:creator>neha_shirsath</dc:creator>
      <dc:date>2017-07-21T10:09:02Z</dc:date>
    </item>
  </channel>
</rss>

