<?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: Cache Warming in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461091#M1273995</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no feature out of the box like that, no.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have achieved a similar thing using a copy of QlikView Desktop and the API.&amp;nbsp; Write some VBscript which cycles around some of your common listboxes.&amp;nbsp; It can then be scheduled as a Supporting Task in Publisher following your Reload and Distribution task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 24 Nov 2012 13:57:23 GMT</pubDate>
    <dc:creator>dde</dc:creator>
    <dc:date>2012-11-24T13:57:23Z</dc:date>
    <item>
      <title>Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461090#M1273994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand that there is a pre-load functionality in QVS, but is there a feature equivalent to pre-caching or cache-warming? If anyone can point me to the right direction, it would be great. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461090#M1273994</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461091#M1273995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no feature out of the box like that, no.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have achieved a similar thing using a copy of QlikView Desktop and the API.&amp;nbsp; Write some VBscript which cycles around some of your common listboxes.&amp;nbsp; It can then be scheduled as a Supporting Task in Publisher following your Reload and Distribution task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Nov 2012 13:57:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461091#M1273995</guid>
      <dc:creator>dde</dc:creator>
      <dc:date>2012-11-24T13:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461092#M1273996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Dave.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Nov 2012 01:54:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461092#M1273996</guid>
      <dc:creator />
      <dc:date>2012-11-26T01:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461093#M1273997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do u have any example? How to start?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Nov 2013 23:45:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461093#M1273997</guid>
      <dc:creator />
      <dc:date>2013-11-19T23:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461094#M1273998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Two potential ways:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Use the VBScript idea as I mentioned.&amp;nbsp; I suggest you get the API Guide:&lt;A _jive_internal="true" href="https://community.qlik.com/docs/DOC-2640"&gt;http://community.qlik.com/docs/DOC-2640&lt;/A&gt; .&lt;/LI&gt;&lt;LI&gt;An alternative is to use the Load Testing tools at &lt;A _jive_internal="true" href="https://community.qlik.com/docs/DOC-2705" title="http://community.qlik.com/docs/DOC-2705"&gt;http://community.qlik.com/docs/DOC-2705&lt;/A&gt; . Build a script to simulate testing but with a single user.&amp;nbsp; You could then batch run this from Publisher.&lt;BR /&gt; &lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 04:32:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461094#M1273998</guid>
      <dc:creator>dde</dc:creator>
      <dc:date>2013-11-20T04:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461095#M1273999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you. After first app with 500 mln you know, how it is important &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 05:31:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461095#M1273999</guid>
      <dc:creator />
      <dc:date>2013-11-20T05:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461096#M1274000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No worries.&amp;nbsp; Of course your first priority is to get the data model perfect, this just makes things even better.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 05:33:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461096#M1274000</guid>
      <dc:creator>dde</dc:creator>
      <dc:date>2013-11-20T05:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461097#M1274001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yeah,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i'am during model perfection. But with this data volume each mutation (all almost clear stars, minimal use of set analysis) without cache response time is on the 30 s. level. With ready cache it is &lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;immediately. &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;Of course i know, that it is impossible to prepare cache with all potential users selection states. I think, cache will be very big, but (using pareto) probably 20% of cache will have 80% important users selections states. And this i why it is important to know, what users will be looking for in your big app.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;regards&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="short_text" lang="en"&gt;&lt;SPAN class="hps"&gt;Darek&lt;BR /&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 05:40:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461097#M1274001</guid>
      <dc:creator />
      <dc:date>2013-11-20T05:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: Cache Warming</title>
      <link>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461098#M1274002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Fair enough.&amp;nbsp; Work out what the primary route most users take (e.g. what listboxes) and then have your script loop around those.&amp;nbsp; You could then schedule this in Publisher to follow your Reload.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Nov 2013 08:30:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Cache-Warming/m-p/461098#M1274002</guid>
      <dc:creator>dde</dc:creator>
      <dc:date>2013-11-20T08:30:30Z</dc:date>
    </item>
  </channel>
</rss>

