Performance issues with ePolicy Orchestrator and SQL on systems running more than one CPU
Last Modified: 2023-07-14 08:25:40 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Performance issues with ePolicy Orchestrator and SQL on systems running more than one CPU
Technical Articles ID:
KB79310
Last Modified: 2023-07-14 08:25:40 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x Microsoft SQL Server - all supported versions For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator. ProblemSystems with more than one microprocessor or CPU can experience performance issues with ePO and SQL, including, but not limited to, the following:
CauseOne of the issues is an incorrect Maximum Degree of Parallelism (MAXDOP) setting. When the SQL Server runs on a computer with more than one microprocessor or CPU, it detects the best degree of parallelism; that is, the number of processors employed to run a single statement for each parallel plan execution.
You can use the
For more information about the Solution
If MAXDOP is set to 1, set the value to 0, which is the default value, so that SQL uses all available processors. To change this setting, perform the following steps in
NOTE: Limit the number of CPUs used by SQL for executing parallel statements if For recommendations and guidelines for the Affected ProductsLanguages:This article is available in the following languages: |
|