QlikView Server - The system is currently overloaded (CPU limit), tasks do not start (QlikView May 2023 SR1)

[maxgro]

Qlik LoadBalancer log shows the system is overloaded due to CPU load and tasks are not starting.
From the Windows task manager the CPU load is low, less than 20%.
It appears that QlikView is not calculating the CPU load correctly.
Temporarily bypassed by setting  "CpuOverloadLimit" value="101" in QVDistributionService.exe.config.
Does anyone have a better solution?

Thank you

QlikView May 2023 SR1, SLK license, with publisher

LoadBalancer log

20231206T091014.732+0100 Information LoadMeasurer: The system is currently overloaded. Memory value: 3,74045830355376 CPU value: 88,3204727172852
20231206T091115.713+0100 Information LoadMeasurer: The system is not overloaded anymore.
20231206T104907.248+0100 Information LoadMeasurer: The system is currently overloaded. Memory value: 20,9417568397414 CPU value: 100

[Chip_Matejowsky · Accepted solution]

Hi @maxgro,

You can make changes to the values in the %Program Files%\QlikView\Distribution Service\DistributionService.exe.config file to improve how QDS utilizes CPU cycles.  Refer to Qlik Support article QlikView Distribution Service/ Publisher (QDS) high CPU usage without active tasks for details. Note that this article contains some of the same information that is included in the Scaling the QlikView Publisher whitepaper I provided yesterday. If you have multiple Publisher nodes, then you'll want to be sure to make changes to the DistributionService.exe.config file on all nodes.

I cannot stress how helpful the Scaling the QlikView Publisher whitepaper is. Typically, Qlik Support uses it to assist customers in configuring their Publisher to optimize performance, oftentimes in extremely large Publisher environments.

Please note that the QDS utilization of CPU can be very sudden and not always correctly captured by Windows Task Manager. I have seen this so many times.

Best Regards