<?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: Qlik Sense Repository on dedicated node? in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245154#M8377</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Repository service must be on each node. Dedicate PostreSQL and Share Folder server give you more perfomance. Also you can spesial speed NAS or spesial Database server. &lt;/P&gt;&lt;P&gt;Qlik Sense server need much RAM. &lt;/P&gt;&lt;P&gt;NAS server need speed disks&lt;/P&gt;&lt;P&gt;Database server some else.&lt;/P&gt;&lt;P&gt;To achieve optimum performance it is difficult to combine all these factors in a single server&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Feb 2017 12:05:00 GMT</pubDate>
    <dc:creator>korsikov</dc:creator>
    <dc:date>2017-02-22T12:05:00Z</dc:date>
    <item>
      <title>Qlik Sense Repository on dedicated node?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245153#M8376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;Hi there,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;How important is it to have Repository/PostgreSQL running on a dedicated node in a multi-node environment. What are the pros and cons of this architectural approach?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;DV&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2017 11:35:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245153#M8376</guid>
      <dc:creator>IAMDV</dc:creator>
      <dc:date>2017-02-22T11:35:15Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository on dedicated node?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245154#M8377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Repository service must be on each node. Dedicate PostreSQL and Share Folder server give you more perfomance. Also you can spesial speed NAS or spesial Database server. &lt;/P&gt;&lt;P&gt;Qlik Sense server need much RAM. &lt;/P&gt;&lt;P&gt;NAS server need speed disks&lt;/P&gt;&lt;P&gt;Database server some else.&lt;/P&gt;&lt;P&gt;To achieve optimum performance it is difficult to combine all these factors in a single server&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2017 12:05:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245154#M8377</guid>
      <dc:creator>korsikov</dc:creator>
      <dc:date>2017-02-22T12:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository on dedicated node?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245155#M8378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt;Thank you for the inputs. Is the dedicated Repository node same spec as other nodes? To be more specific - does the Repository node needs to have &lt;/SPAN&gt;same&lt;SPAN style="font-family: calibri, verdana, arial, sans-serif;"&gt; amount of RAM and CPU?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2017 13:42:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245155#M8378</guid>
      <dc:creator>IAMDV</dc:creator>
      <dc:date>2017-02-22T13:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository on dedicated node?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245156#M8379</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it makes no sense to install a separate repository service.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Feb 2017 07:12:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245156#M8379</guid>
      <dc:creator>korsikov</dc:creator>
      <dc:date>2017-02-24T07:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense Repository on dedicated node?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245157#M8380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am investigating the option of installing the &lt;SPAN style="font-size: 13.3333px;"&gt;infrastructure with &lt;/SPAN&gt;separate Repository and FileShare nodes (based on Sept 2017 release).... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just looking for PROS/CONS for using these additional nodes... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciate some suggestions/shared experience.... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vlad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Sep 2017 18:59:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-Repository-on-dedicated-node/m-p/1245157#M8380</guid>
      <dc:creator>vlad_komarov</dc:creator>
      <dc:date>2017-09-29T18:59:00Z</dc:date>
    </item>
  </channel>
</rss>

