<?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: pixel perfect on demand performance in Qlik NPrinting</title>
    <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998537#M37446</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Performances depend on many factors. Refer to the page&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm" target="_blank"&gt;https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Generation time also depends on the structure of the report. For example, multiple nested levels will increase it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also suggest you monitor the Qlik Sense server workload during reports generation and avoid using section access (that is supported) but use native Qlik NPrinting filters instead.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ruggero&lt;/P&gt;</description>
    <pubDate>Mon, 31 Oct 2022 10:33:34 GMT</pubDate>
    <dc:creator>Ruggero_Piccoli</dc:creator>
    <dc:date>2022-10-31T10:33:34Z</dc:date>
    <item>
      <title>pixel perfect on demand performance</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998038#M37440</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have noticed the first time I run an On-Demand Pixel Perfect Report the run time could be about 2 minutes.&amp;nbsp; This is a large report with about 20 pages.&lt;/P&gt;
&lt;P&gt;The second time I run the report it is around 30 seconds.&lt;/P&gt;
&lt;P&gt;Is there a way to improve the performance the first time the report is run?&lt;/P&gt;
&lt;P&gt;Thank You,&lt;/P&gt;
&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2022 10:04:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998038#M37440</guid>
      <dc:creator>mstoler</dc:creator>
      <dc:date>2022-10-28T10:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: pixel perfect on demand performance</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998039#M37441</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/6140"&gt;@mstoler&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe it is because of cache benefit and loading app to the memory . I dont think you can do much about it. I will say that this goes down to well known roots of how Qlik engine works&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2022 10:08:40 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998039#M37441</guid>
      <dc:creator>Lech_Miszkiewicz</dc:creator>
      <dc:date>2022-10-28T10:08:40Z</dc:date>
    </item>
    <item>
      <title>Re: pixel perfect on demand performance</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998058#M37443</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/6140"&gt;@mstoler&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;When you execute a task or request an on-demand report NPrinting starts to open connections to qlik app (min 1 and max, by default, number of core of NPritning server) once at time, it doesn't open all available connections at start. After complete the request NPrinting doesn't close them, so when you request a second report NPrinting has some connection open.&lt;/P&gt;
&lt;P&gt;You can monit the allocation of resolver at this hidden link of nprinting console &lt;A href="https://nprintingserver:4993/#/admin/plan" target="_blank"&gt;https://nprintingserver:4993/#/admin/plan&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;The rightest columns with four exadecimal digits identify the last digits of NPritning Engine, for each of them you could see how many connections are open on each of avilable engine. When you see a blue number means that np is opening a connection, instead yellow means np is closing a connection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2022 11:05:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998058#M37443</guid>
      <dc:creator>andregas</dc:creator>
      <dc:date>2022-10-28T11:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: pixel perfect on demand performance</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998537#M37446</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Performances depend on many factors. Refer to the page&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm" target="_blank"&gt;https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/DeployingQVNprinting/Performance.htm&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Generation time also depends on the structure of the report. For example, multiple nested levels will increase it.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also suggest you monitor the Qlik Sense server workload during reports generation and avoid using section access (that is supported) but use native Qlik NPrinting filters instead.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ruggero&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 10:33:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998537#M37446</guid>
      <dc:creator>Ruggero_Piccoli</dc:creator>
      <dc:date>2022-10-31T10:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: pixel perfect on demand performance</title>
      <link>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998539#M37447</link>
      <description>&lt;P&gt;Thank You.&lt;/P&gt;
&lt;P&gt;It takes about 3 minutes the first time.&lt;/P&gt;
&lt;P&gt;The second time it drops to about 30 seconds.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Michael&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 10:35:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-NPrinting/pixel-perfect-on-demand-performance/m-p/1998539#M37447</guid>
      <dc:creator>mstoler</dc:creator>
      <dc:date>2022-10-31T10:35:47Z</dc:date>
    </item>
  </channel>
</rss>

