<?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: QlikView server processing of client requests and timeouts in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020006#M1253169</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks to both of you for your help.&amp;nbsp; Time to get on with getting another supermarket lane set up I think. &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/laugh.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Apr 2016 01:45:37 GMT</pubDate>
    <dc:creator>reanfadyl</dc:creator>
    <dc:date>2016-04-04T01:45:37Z</dc:date>
    <item>
      <title>QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020001#M1253154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;‌Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone shed some light on what order QlikView Server/web server processes end user selections?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if one user asks for a table chart that has say 600k individually calculated data points (i know this is bad practices but this is just theoretical), and then a second user asks for for a line chart that has say 16 calculated data points, will the second user have to wait for the first user to get their answer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Will the second user potentially timeout before they get their result?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does the number of CPU cores available make a difference?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rean&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ps I have read the scalability test white papers etc. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020001#M1253154</guid>
      <dc:creator>reanfadyl</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020002#M1253157</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If I read this correctly&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3214"&gt;Logical Inference and Aggregations&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the calculations should be asynchronous and multithreaded. So "600k" user should not block "16" user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Probably &lt;A href="https://community.qlik.com/qlik-users/4003"&gt;hic&lt;/A&gt;‌ can explain this much better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Stefan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2016 20:07:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020002#M1253157</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2016-03-30T20:07:30Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020003#M1253160</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;‌Thanks I took a look at HIC's post but it is not entirely clear if it is asynchronous across multiple users e.g. but&amp;nbsp; yes The&amp;nbsp; aggregations for each visible object for one user are definitley async&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2016 20:28:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020003#M1253160</guid>
      <dc:creator>reanfadyl</dc:creator>
      <dc:date>2016-03-30T20:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020004#M1253163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All requests are asynchronous and multithreaded. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A heavy request will take most of the processing power also across multiple cores, so that other heavy requests will have to wait. But there is also &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;a function that should prevent a heavy calculation from taking &lt;EM&gt;&lt;STRONG&gt;all&lt;/STRONG&gt;&lt;/EM&gt; the processing power, so there will always remain some &lt;/SPAN&gt;capacity for smaller requests. Like a fast queue in the supermarket.&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, 31 Mar 2016 07:49:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020004#M1253163</guid>
      <dc:creator>hic</dc:creator>
      <dc:date>2016-03-31T07:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020005#M1253166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, Henric.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rean,&lt;/P&gt;&lt;P&gt;and to answer your last question, adding more ressources to share between users should definitely help&lt;/P&gt;&lt;P&gt;(well, you already know the scalability white papers).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Mar 2016 10:04:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020005#M1253166</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2016-03-31T10:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: QlikView server processing of client requests and timeouts</title>
      <link>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020006#M1253169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks to both of you for your help.&amp;nbsp; Time to get on with getting another supermarket lane set up I think. &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/laugh.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Apr 2016 01:45:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/QlikView-server-processing-of-client-requests-and-timeouts/m-p/1020006#M1253169</guid>
      <dc:creator>reanfadyl</dc:creator>
      <dc:date>2016-04-04T01:45:37Z</dc:date>
    </item>
  </channel>
</rss>

