<?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: application performance tuning in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364387#M135574</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sonika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Application performance tuning can be done in few ways.&lt;/P&gt;&lt;P&gt;when specificly you are asking about pivote tables, how many rows of data you have in pivote tables and how long it's going for you to access data from pivote table.&lt;/P&gt;&lt;P&gt;these are critical issue when you are dealing with pivote table, if you are dealing with huge set of data in pivotes it's not advisory to use many dimensions so that when you are pivoting to the last dimension performance will be impacted. &lt;/P&gt;&lt;P&gt;Mean while if you are dealing with data aggregation try to aggregate them in script side instead of doing them on UI/ by eexpressions.&lt;/P&gt;&lt;P&gt;If possible try to apply fiters on pivote selections which helps you to reduce data in tyour table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Meher&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Jun 2012 16:07:45 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-06-22T16:07:45Z</dc:date>
    <item>
      <title>application performance tuning</title>
      <link>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364386#M135573</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;&lt;/P&gt;&lt;P&gt;Please provide me some ideas on performance tuning of a qlikview application, the general ones as well as the ones specific to the usage of pivot tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your reponses will be of tremendous help to me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sonika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 15:21:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364386#M135573</guid>
      <dc:creator>sonikajain</dc:creator>
      <dc:date>2012-06-22T15:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: application performance tuning</title>
      <link>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364387#M135574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sonika,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Application performance tuning can be done in few ways.&lt;/P&gt;&lt;P&gt;when specificly you are asking about pivote tables, how many rows of data you have in pivote tables and how long it's going for you to access data from pivote table.&lt;/P&gt;&lt;P&gt;these are critical issue when you are dealing with pivote table, if you are dealing with huge set of data in pivotes it's not advisory to use many dimensions so that when you are pivoting to the last dimension performance will be impacted. &lt;/P&gt;&lt;P&gt;Mean while if you are dealing with data aggregation try to aggregate them in script side instead of doing them on UI/ by eexpressions.&lt;/P&gt;&lt;P&gt;If possible try to apply fiters on pivote selections which helps you to reduce data in tyour table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Meher&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 16:07:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364387#M135574</guid>
      <dc:creator />
      <dc:date>2012-06-22T16:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: application performance tuning</title>
      <link>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364388#M135575</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;Other thing that is important and is related to the entire application is the data modeling, avoid synthetic keys and disconnected fields (without relationship between its tables) in the same object.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cesar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 16:54:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364388#M135575</guid>
      <dc:creator>cesaraccardi</dc:creator>
      <dc:date>2012-06-22T16:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: application performance tuning</title>
      <link>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364389#M135576</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is a helpful post on performance tunning. Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/thread/18473?start=0&amp;amp;tstart=0"&gt;http://community.qlik.com/thread/18473?start=0&amp;amp;tstart=0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ash&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jun 2012 17:28:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/application-performance-tuning/m-p/364389#M135576</guid>
      <dc:creator>regowins</dc:creator>
      <dc:date>2012-06-22T17:28:49Z</dc:date>
    </item>
  </channel>
</rss>

