<?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 Poor performance after upgrade to april-2018 in Scalability</title>
    <link>https://community.qlik.com/t5/Scalability/Poor-performance-after-upgrade-to-april-2018/m-p/29360#M49</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I upgraded a qlik sense multi node enviroment to april-18 version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that, I noticed a poor performance of my schedule tasks during the night (almost 2 hours longer).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that I missed some specific configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We didnt change anything in the hardware and infra&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any clue about that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2018 15:05:42 GMT</pubDate>
    <dc:creator>igorgois_</dc:creator>
    <dc:date>2018-05-14T15:05:42Z</dc:date>
    <item>
      <title>Poor performance after upgrade to april-2018</title>
      <link>https://community.qlik.com/t5/Scalability/Poor-performance-after-upgrade-to-april-2018/m-p/29360#M49</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I upgraded a qlik sense multi node enviroment to april-18 version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that, I noticed a poor performance of my schedule tasks during the night (almost 2 hours longer).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that I missed some specific configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We didnt change anything in the hardware and infra&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any clue about that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2018 15:05:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Poor-performance-after-upgrade-to-april-2018/m-p/29360#M49</guid>
      <dc:creator>igorgois_</dc:creator>
      <dc:date>2018-05-14T15:05:42Z</dc:date>
    </item>
    <item>
      <title>Re: Poor performance after upgrade to april-2018</title>
      <link>https://community.qlik.com/t5/Scalability/Poor-performance-after-upgrade-to-april-2018/m-p/29361#M50</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is an issue with ODBC performance in the April release. It's being worked on under bug ID QLIK-&lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri',sans-serif;"&gt;88243. Talk to your support contact at Qlik and see if it could be related to that. Current suggestions for workaround is to revert to Feburary release or use QV Desktop to perform the extracts. You could also try to use an OLE DB connection. &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 May 2018 10:16:46 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/Poor-performance-after-upgrade-to-april-2018/m-p/29361#M50</guid>
      <dc:creator>larshilkenl</dc:creator>
      <dc:date>2018-05-17T10:16:46Z</dc:date>
    </item>
  </channel>
</rss>

