<?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: Group by Single threaded, why? in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Group-by-Single-threaded-why/m-p/1309929#M407284</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is how &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ describes it:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;
&lt;P style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;...The script evaluation is inherently different from the analysis evaluation of data. In the script, the order of the records matter and this poses limitiations on the algorithm. We have made the script execution multi-threaded, but in principle the multi threading is on a record per record base: A thread needs to wait for the other threads to finish before it can process the next record.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Further, both the crosstable transformation and the &lt;STRONG&gt;group by&lt;/STRONG&gt; transformation involve multiple records, which also makes multi threading difficult (or maybe impossible).&lt;/P&gt;


&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The discussion thread is here : &lt;A href="https://community.qlik.com/thread/50589"&gt;Single-threaded calculations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;I can't claim that I fully understand this though. I thought at least part of it could have been gone parallel in execution.&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 09 May 2017 13:19:15 GMT</pubDate>
    <dc:creator>tresB</dc:creator>
    <dc:date>2017-05-09T13:19:15Z</dc:date>
    <item>
      <title>Group by Single threaded, why?</title>
      <link>https://community.qlik.com/t5/QlikView/Group-by-Single-threaded-why/m-p/1309928#M407283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Anyone knows why Group By inside qlikview Script is single threaded&amp;nbsp; (only uses one cpu core).?&lt;/P&gt;&lt;P&gt;Am I doing something wrong ( ex server settings, NUMA?) or is this the default behavior? Is there a way to overcome it (workaround or something)&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS. Logically I can do group by in a large dataset by splitting the dataset to x parts (1 per available core) group by each part , and then group by the results.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 May 2017 13:06:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Group-by-Single-threaded-why/m-p/1309928#M407283</guid>
      <dc:creator />
      <dc:date>2017-05-09T13:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: Group by Single threaded, why?</title>
      <link>https://community.qlik.com/t5/QlikView/Group-by-Single-threaded-why/m-p/1309929#M407284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is how &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ describes it:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;
&lt;P style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;...The script evaluation is inherently different from the analysis evaluation of data. In the script, the order of the records matter and this poses limitiations on the algorithm. We have made the script execution multi-threaded, but in principle the multi threading is on a record per record base: A thread needs to wait for the other threads to finish before it can process the next record.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;Further, both the crosstable transformation and the &lt;STRONG&gt;group by&lt;/STRONG&gt; transformation involve multiple records, which also makes multi threading difficult (or maybe impossible).&lt;/P&gt;


&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The discussion thread is here : &lt;A href="https://community.qlik.com/thread/50589"&gt;Single-threaded calculations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;I can't claim that I fully understand this though. I thought at least part of it could have been gone parallel in execution.&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 May 2017 13:19:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Group-by-Single-threaded-why/m-p/1309929#M407284</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2017-05-09T13:19:15Z</dc:date>
    </item>
  </channel>
</rss>

