--- title: "How Threat Prevention limits CPU usage" slug: "how-threat-prevention-limits-cpu-usage" tags: ["Product Usage", "ENS 10.7.x", "Endpoint Security"] updated: 2026-09-14T20:39:03Z published: 2026-09-14T20:39:03Z canonical: "docs.trellix.com/how-threat-prevention-limits-cpu-usage" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # How Threat Prevention limits CPU usage To optimize the performance of a client system, you can restrict the CPU usage of on-demand scans. The CPU utilization of a client system increases during an on-demand scan. With other processes and services running parallel to the on-demand scan, the CPU utilization can rise up to 100%. The high CPU utilization affects the performance of the system. You can prevent this situation by enabling **Limit maximum CPU usage** and defining a threshold percentage for CPU usage. During an on-demand scan, the CPU utilization value doesn't exceed the threshold value. The threshold value is inversely proportional to the time needed to complete the scan. The higher the threshold value, the quicker the scan finishes. The **Limit maximum CPU usage** option restricts CPU usage for full scans, quick scans, and custom scans. This option only applies to scanning files. It doesn't limit CPU usage when scanning other items, such as memory, registry, and boot sectors. > [!NOTE] > Note > > This option is available only when the **Scan anytime** option is selected.