<?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 QVD optimized load benchmark in Scalability</title>
    <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594604#M346</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are your IO-benchmarks when running an optimized QVD load?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a new shiny server on a fat RAID. It shows a throughput of a few hundred MByte/sec when reading/writing files. An optimized load of a QVD on same server gets to a 10-30MByte/sec max. Only one CPU core is fully used and the others are idle, or the load jumps between the cores.&lt;/P&gt;&lt;P&gt;I wonder what might be the bottleneck? Is it the intrinsically single-threaded nature of the QVD load process or something else on that server?&lt;/P&gt;&lt;P&gt;Could this be some setting or an antivirus that limits this to a single core?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 03 Apr 2014 04:13:12 GMT</pubDate>
    <dc:creator />
    <dc:date>2014-04-03T04:13:12Z</dc:date>
    <item>
      <title>QVD optimized load benchmark</title>
      <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594604#M346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What are your IO-benchmarks when running an optimized QVD load?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a new shiny server on a fat RAID. It shows a throughput of a few hundred MByte/sec when reading/writing files. An optimized load of a QVD on same server gets to a 10-30MByte/sec max. Only one CPU core is fully used and the others are idle, or the load jumps between the cores.&lt;/P&gt;&lt;P&gt;I wonder what might be the bottleneck? Is it the intrinsically single-threaded nature of the QVD load process or something else on that server?&lt;/P&gt;&lt;P&gt;Could this be some setting or an antivirus that limits this to a single core?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2014 04:13:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594604#M346</guid>
      <dc:creator />
      <dc:date>2014-04-03T04:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: QVD optimized load benchmark</title>
      <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594605#M347</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Someone like &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;Henric Cronström&lt;/A&gt; would be best placed to answer about the core usage.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may find that IO is relatively low on the QVD load as the file is so well compressed it doesn't take much disk space (and therefore IO requirement).&amp;nbsp; The work is around indexing and associating in RAM once the file is loaded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2014 08:31:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594605#M347</guid>
      <dc:creator>stevedark</dc:creator>
      <dc:date>2014-04-03T08:31:37Z</dc:date>
    </item>
    <item>
      <title>Re: QVD optimized load benchmark</title>
      <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594606#M348</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My guess is that the bottleneck is disc access (although you say that throughput could be a few hundred MB/s but is only 10-30MB/s). Do you get the same load time the first time you read the file (read from disc) as you get the second time you read it (read from OS cache)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HIC &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2014 10:07:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594606#M348</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2014-04-03T10:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: QVD optimized load benchmark</title>
      <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594607#M349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This is my view on this topic.&lt;/P&gt;&lt;P&gt;Reading a stream of qvd data is not a cpu intensive operation. It is in fact single threaded, unless the script performs&amp;nbsp; data transformations. &lt;/P&gt;&lt;P&gt;For QlikView a reload will only read one file/stream at the time per qv.exe or qvb.exe (Publisher reload engine).&lt;/P&gt;&lt;P&gt;Many parallel instances you will put a higher load on the disk.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "core jumping" is, to my knowledge, under the operating systems control.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/lars&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Apr 2014 12:44:05 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594607#M349</guid>
      <dc:creator>lse</dc:creator>
      <dc:date>2014-04-03T12:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: QVD optimized load benchmark</title>
      <link>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594608#M350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for all the feedback. I will have to experiment to reflect on that. &lt;/P&gt;&lt;P&gt;But nobody has given their benchmark away. What is your highest throughput when reading in the QVD optimized files?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Apr 2014 06:13:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Scalability/QVD-optimized-load-benchmark/m-p/594608#M350</guid>
      <dc:creator />
      <dc:date>2014-04-04T06:13:03Z</dc:date>
    </item>
  </channel>
</rss>

