How to minimize the performance impact of the ad-hoc evaluation option in SD Softwared Based Policy ?
search cancel

How to minimize the performance impact of the ad-hoc evaluation option in SD Softwared Based Policy ?

book

Article ID: 257028

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation - Software Delivery CA Client Automation

Issue/Introduction

When a Software Based Policy has ad-hoc evaluation option enabled (ex: Enable ad-hoc target evaluation for this group - Always when targets report their inventory), a lot of "Target Evaluation" tasks could be created.
 
 
This could generate a lot of work for Domain Manager :
 
- Evaluation of linked dynamic group.
- Building of SD Job Container.
 
 
How to minimize the performance impact of the ad-hoc option ?

Environment

Client Automation - Any Versions

Cause

By default PolMan plugin on Domain Manager is using these 2 parameters for ad-hoc option :
 
DSM/Software Delivery/Manager/CompEvalTaskDelayActivationTime = 2
DSM/Software Delivery/Manager/CompEvalTaskCompCountLimit = 10
 
This means that ad-hoc Software Policy are evaluated :
 
- When 10 machines have reported their inventory within 2 minutes
or
- After 2 minutes (if the limit of 10 machines is not reached).
 
 
Example 1 :
 
10:00:00 - Computer C1 reports its inventory. If there is no "Target Evaluation" Task already, a "Target Evaluation" Task is created for this machine. This Task is scheduled to be evaluated in 2 minutes (10:02:00)
10:00:25 - Computer C2 reports its inventory. It is added in "Target Evaluation" Task (2 computers in the list)
10:02:00 - PolMan executes the evaluation "Target Evaluation" task for the 2 computers
 
 
Example 2 :
 
10:00:00 - Computer C1 reports its inventory. If there is no "Target Evaluation" Task already, a "Target Evaluation" Task is created for this machine. This Task is scheduled to be evaluated in 2 minutes (10:02:00)
10:00:25 - Computer C2 reports its inventory. It is added in "Target Evaluation" Task (2 computers in the list)
10:00:45 - Computers C3 to C10 reports its inventory. They are added in "Target Evaluation" Task (10 computers in the list) 
10:00:46 - PolMan executes the evaluation "Target Evaluation" task for the 10 computers
 
 
This could generate performance problem on Domain Manager if 2000 computers report their inventory between 12h and 14h for example. This could generate a maximum of 200 "Target Evaluation" Task.

Resolution

To minimize the performance impact of ad-hoc option these 2 parameters could be changed in Configuration Policy applied on Domain Manager.

Example :

DSM/Software Delivery/Manager/CompEvalTaskDelayActivationTime = 10
DSM/Software Delivery/Manager/CompEvalTaskCompCountLimit = 50

ad-hoc Software Policy are evaluated :
 
- When 50 machines have reported their inventory within 10 minutes
or
- After 10 minutes (if the limit of 50 machines is not reached).

 

If 2000 computers report their inventory between 12h and 14h, this could generate 40 "Target Evaluation" Task.