<?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: Publisher Reload Issue in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745641#M1261376</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you seen any perfromacne degradation if we use more cpu cores on publisher box?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Nov 2014 22:57:36 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-11-03T22:57:36Z</dc:date>
    <item>
      <title>Publisher Reload Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745638#M1261368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are on VM 8 cores and 64 GB. It seems tihs reload consumves all resources and its huge and when this happens others are waiting for resources. if we see 95% of cpu used by this job most of the time... thne should we cluster out publisher node or move to Physical box for data reloads. We had 16 cores but data reload were taking more times so we moved it down to 8 cores.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Reload Issue.png" class="jive-image" src="/legacyfs/online/70260_Reload Issue.png" style="width: 620px; height: 337px;" /&gt;&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/Publisher-Reload-Issue/m-p/745638#M1261368</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Publisher Reload Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745639#M1261372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Put publisher on another box, but as a first try and revisit the script and break it down to make the reload less intense.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 20:06:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745639#M1261372</guid>
      <dc:creator>nam</dc:creator>
      <dc:date>2014-10-31T20:06:24Z</dc:date>
    </item>
    <item>
      <title>Re: Publisher Reload Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745640#M1261374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry just noticed you are on 11.0 SR2... Upgrade to the latest version first&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 31 Oct 2014 20:07:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745640#M1261374</guid>
      <dc:creator>nam</dc:creator>
      <dc:date>2014-10-31T20:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: Publisher Reload Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745641#M1261376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have you seen any perfromacne degradation if we use more cpu cores on publisher box?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Nov 2014 22:57:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745641#M1261376</guid>
      <dc:creator />
      <dc:date>2014-11-03T22:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: Publisher Reload Issue</title>
      <link>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745642#M1261378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;definitely move to a physical box&lt;/P&gt;&lt;P&gt;publisher tasks and data loads generally be more memory intensive not CPU&lt;/P&gt;&lt;P&gt;if you suspect two three tasks which cause performance issues you can try improving them&lt;/P&gt;&lt;P&gt;I've experimented such improvements may reduce Memory &amp;amp; CPU usage 99% for a task.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Nov 2014 23:18:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Publisher-Reload-Issue/m-p/745642#M1261378</guid>
      <dc:creator />
      <dc:date>2014-11-03T23:18:23Z</dc:date>
    </item>
  </channel>
</rss>

