The number of requests (inter-process communication) that come to the McAfee Agent service to fetch the policies is substantial. As a result, the McAfee Agent service is busy reading (fetching) and sending policy data to each managed product through inter-process communication.
The CPU utilization during policy enforcement is directly linked to both of the following:
- The number of policies, specifically, the number of sections and Uniform Resource Identifiers (URIs).
- The number of managed products registered for policy enforcements.
Suppose that the number of URIs configured in the policies is
M, and the number of sections is
N. As an average for each URI, the average number of requests to the McAfee Agent service is (
M*N + N +1).
If the number of managed products registered for policy enforcements is
K, the average number of requests to the McAfee Agent service is
(M*N + N +1)*K. So, the CPU utilization is higher while enforcing policies.
When large complex policies are created for many McAfee products,
masvc.exe takes a significant amount of time to apply the policies. The process consumes a considerable amount of CPU. You can also observe that the issue has an overall impact on the computer's performance. The performance issue can last more than 10 minutes, during which you don’t see a reduction in
masvc.exe CPU.
