<?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: June 2018: Optimizing the Insight Advisor in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137861#M9705</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Dear Michael&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Grateful for your answer.&lt;/P&gt;&lt;P&gt;I share some of the cases that are evident after carrying out the Qliksense and Nprinitng update from the January 2018 versions to the June 2018 version:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The load of the METADATA from Nprinitng, now takes more time, in some applications it reaches an increase of up to 30 minutes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Some reports that in Npriniting, are generated as PDF and that generally can take 30 seconds, but after the update to the June 2018 version, they can take up to 9 minutes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The reports in Npriniting in excel format took approximately 5 minutes, but after the update to the June 2018 version, they take more than 10 minutes to generate or even fail to generate and show "Time out" error. In other occasions they are generated but the information is incomplete, that is, out of 30 columns that make up the excel report, 20 columns are empty.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The RAM of the server of Qlik sense june 2018, always remains high and is never released, even on occasion consumes 99% of it, being necessary to restart the engine service.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The amount of RAM and processors has been increased to the servers of QlikSense and Nprinting to try to mitigate these problems and the problems continue with the June 2018 versions.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The solution that is being suggested is to downgrade the version prior to the update to validate if these slow behaviors are solved.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;&lt;STRONG style="text-decoration: underline;"&gt;QlikSense server configuration:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;&lt;IMG alt="qliksense.PNG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/211755_qliksense.PNG" style="height: auto;" /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;STRONG style="text-decoration: underline;"&gt;Nprinting server configuration:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;IMG alt="npriniting.PNG" class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/211756_npriniting.PNG" style="height: auto;" /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I would like to know if with these configurations in the servers, is it enough for the correct functioning of Qliksense and Nprinting in its June 2018 versions?&lt;/P&gt;&lt;P&gt;Thank you very much again for collaboration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hugo Simancas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 24 Aug 2018 13:40:01 GMT</pubDate>
    <dc:creator>hugoasmqlikview</dc:creator>
    <dc:date>2018-08-24T13:40:01Z</dc:date>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137858#M9702</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Michael Tarallo, after upgrading to the Qlik Sense Server June 2018 version. We have noticed that now the server where QlikSense is installed uses more resources, especially RAM. Is this normal? Does the new version with the new features of Insight Advisor cost more resources? For example now the objects take much longer to show the information in tables and graphics, even to move from the view of editing to the visualization !!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there an option to temporarily disable the functionality of Insight Advisor, and Alternative chart suggestions: both in the Server version and in the desktop?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I remain attentive to your comments.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hugo Simancas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Aug 2018 21:40:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137858#M9702</guid>
      <dc:creator>hugoasmqlikview</dc:creator>
      <dc:date>2018-08-13T21:40:58Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137859#M9703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hugo - thanks for this. I branched this to a new discussion thread - let me review this with some people and myself or they will get back to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael Tarallo &lt;/P&gt;&lt;P&gt;Qlik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2018 14:56:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137859#M9703</guid>
      <dc:creator>Michael_Tarallo</dc:creator>
      <dc:date>2018-08-14T14:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137860#M9704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hugo - I just got word from our product's team that Insight Advisor should not affect the current charts. There may be something going on such as logging. If you are a licensed customer, have you brought this to the attention of our Qlik support or your local account rep. They should be able to help you investigate this further. Please let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Aug 2018 17:28:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137860#M9704</guid>
      <dc:creator>Michael_Tarallo</dc:creator>
      <dc:date>2018-08-20T17:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137861#M9705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Dear Michael&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Grateful for your answer.&lt;/P&gt;&lt;P&gt;I share some of the cases that are evident after carrying out the Qliksense and Nprinitng update from the January 2018 versions to the June 2018 version:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The load of the METADATA from Nprinitng, now takes more time, in some applications it reaches an increase of up to 30 minutes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Some reports that in Npriniting, are generated as PDF and that generally can take 30 seconds, but after the update to the June 2018 version, they can take up to 9 minutes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The reports in Npriniting in excel format took approximately 5 minutes, but after the update to the June 2018 version, they take more than 10 minutes to generate or even fail to generate and show "Time out" error. In other occasions they are generated but the information is incomplete, that is, out of 30 columns that make up the excel report, 20 columns are empty.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The RAM of the server of Qlik sense june 2018, always remains high and is never released, even on occasion consumes 99% of it, being necessary to restart the engine service.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The amount of RAM and processors has been increased to the servers of QlikSense and Nprinting to try to mitigate these problems and the problems continue with the June 2018 versions.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The solution that is being suggested is to downgrade the version prior to the update to validate if these slow behaviors are solved.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;&lt;STRONG style="text-decoration: underline;"&gt;QlikSense server configuration:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="en"&gt;&lt;IMG alt="qliksense.PNG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/211755_qliksense.PNG" style="height: auto;" /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;STRONG style="text-decoration: underline;"&gt;Nprinting server configuration:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;IMG alt="npriniting.PNG" class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/211756_npriniting.PNG" style="height: auto;" /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I would like to know if with these configurations in the servers, is it enough for the correct functioning of Qliksense and Nprinting in its June 2018 versions?&lt;/P&gt;&lt;P&gt;Thank you very much again for collaboration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hugo Simancas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2018 13:40:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137861#M9705</guid>
      <dc:creator>hugoasmqlikview</dc:creator>
      <dc:date>2018-08-24T13:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137862#M9706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you solve this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've upgraded to June 2018 this monday with the same slow performance. Yesterday we tried to upgrade to September and check if this version resolve this problem, but it's the same (charts loading and never stop, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally today I've reinstalled our last version (February 2018) because I wasn't able to find any good solution. Really sad.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 16:43:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137862#M9706</guid>
      <dc:creator>silvacarlos</dc:creator>
      <dc:date>2018-09-26T16:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137863#M9707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guys - in these sitauation is best to have a Qlik support person look at this - check out this link that will show you how to open a support case - whether you have a support contract - or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-20429"&gt;Found a bug or a product related problem? You can open a case!&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mike T&lt;/P&gt;&lt;P&gt;Qlik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 16:59:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137863#M9707</guid>
      <dc:creator>Michael_Tarallo</dc:creator>
      <dc:date>2018-09-26T16:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137864#M9708</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One more thing - just throwing this out there - please delete all browser's cache and history - log in again and let us know. If this was wider-spread we would be hearing about it company-wide. I personally have not heard of any issues related to performance from an upgrade. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Sep 2018 17:01:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/137864#M9708</guid>
      <dc:creator>Michael_Tarallo</dc:creator>
      <dc:date>2018-09-26T17:01:10Z</dc:date>
    </item>
    <item>
      <title>Re: June 2018: Optimizing the Insight Advisor</title>
      <link>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/2129562#M91847</link>
      <description>&lt;P&gt;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/12989"&gt;@Michael_Tarallo&lt;/a&gt;&amp;nbsp;Do you know a good resource for understanding Insight Advisor Chat RAM consumption?&amp;nbsp; If I have a large app and it's available for Insight Advisor chat, when is RAM consumption taking place? Could this bog down a tenant?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note: we run both on-prem and cloud so speaking to both types of environments would be helpful.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Mike&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 12:53:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Re-June-2018-Optimizing-the-Insight-Advisor/m-p/2129562#M91847</guid>
      <dc:creator>mgranillo</dc:creator>
      <dc:date>2023-10-18T12:53:13Z</dc:date>
    </item>
  </channel>
</rss>

