
Digital Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
QlikView Distribution Service / Publisher (QDS) high CPU usage without active tasks
Last Update:
Dec 8, 2021 6:58:57 AM
Updated By:
Created date:
Aug 16, 2018 7:52:57 AM
The QlikView Distribution Service (QDS) is consuming a high percentage of overall CPU capacity. No tasks are actively running.
High Memory Handles in task manager for Qlikview Distribution Service are observed.
Environment:
All tasks will be checked no matter if they are enabled or disabled every 500ms in general, the auto adjustment option is not working good when a large number of tasks are disabled or not properly setup.
Risks for high cpu usage are caused by:
- large number of disabled tasks,
- enabled tasks but no source document connected to it.
- a fresh QVPR restore, but unfinished setup
Resolution:
Task files need to be updated regularly. It is possible to adjust the number of tasks updated per thread.
- Stop the QlikView Distribution Service
- Navigate to C:\Program Files\QlikView\Distribution Service\DistributionService.exe.config
- Open the file in a text editor with elevated permissions.
Option 1: Locate the below setting, or add it:<!-- Time to pause between task result cache updates, in milliseconds. --> <add key="TaskResultCacheUpdateSleepTimeBetweenUpdates" value="200"/>
Change the value to 1000, which is 1 sec, do not use a higher value than that.
Option 2 (if the first one does not show results):<!-- Max number of tasks per thread updating the task result cache. Value less than one (1) enabled automatic calibration. --> <add key="TaskResultCacheUpdateMaxTasksPerThread" value="0"/>
Raise the value to lower the baseline QDS CPU consumption. A starting value can be a slightly higher number than the total number of tasks in the deployment. - Save the file
- Start the QlikView Distribution Service
3,442 Views
Comments

Partner - Creator III
2022-10-26
01:37 AM
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
What happens if I lower the value of TaskResultCacheUpdateSleepTimeBetweenUpdates from 200?