We've recently switched our reload processes from using the OCX to using QlikView reload tasks. This was done because the OCX has severe reliability problems and appears to have little or no support with those sorts of issues.
But one of the things we are trying to do is bulk reload multiple documents at the end of a warehouse load process. So consequently, what we want to do is fire off all the document tasks at once, at the point the warehouse load completes. We're using EDX triggering to do this. Is this a reliable way to handle it? Is there any downside or limit to triggering a batch of tasks essentially simultaneously? Is the Qlikview Task Reload process robust enough to handle the multiple requests and properly parallelize the reload processes? We're talking around 20 at the moment, but that has been growing over time. And some of these are fairly large documents that can take anywhere from a few minutes to more than an hour or even more to reload based on the amount of data involved. Since this is deployed to hundreds of customers, we have not attempted to fine-tune any configuration parameters such as CPU affinity, etc., and leave all of those at the defaults, at least initially. We hope we are taking advantage of the QlikView internal threading by submitting all the tasks at once and letting QlikView sort out the threading process. Is this a reasonable way to make use of the reload tasks? And if not, what should we do different?
--
Keith Doyle
