The MA service receives many requests (inter-process communication) to fetch policies. As a result, the MA 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 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. Then, for each URI, the average number of requests received by the MA service is (M*N + N +1).

If the number of managed products registered for policy enforcements is K, then the average number of requests received by the MA service is (M*N + N +1)*K. So, the CPU utilization is higher while enforcing policies.

When large complex policies are created for many products, masvc.exe takes a significant amount of time to apply the policies. This process consumes a considerable amount of CPU.

You can also observe that the issue has an overall impact on the computer's performance. This performance issue can last for more than 10 minutes, during which you don’t see a reduction in the masvc.exe CPU utilization.