Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-0291: Recommended settings in centrifydc.conf for high load CPU servers

Authentication Service ,  

12 April,16 at 11:11 AM

Question:

What are the recommended settings in /etc/centrifydc/centrifydc.conf for high load servers?


Answer:

Here are some recommendations for high load server configuration where the system is creating 100+ requests per second.

adclient.clients.listen.backlog:
This configuration parameter specifies the number of clients which can wait to be serviced.

The parameter value must be an integer zero or greater. For example:
adclient.clients.listen.backlog: 50

If this parameter is not defined in the configuration file, its default value is 50 threads.

For high load servers please use values in the range 200-1000 (This setting may be dependent on OS limits)

adclient.clients.threads:
This configuration parameter specifies the number of threads the Centrify DirectControl daemon pre-allocates for processing client requests.

The parameter value must be an integer zero or greater. If you set this parameter to zero, the Centrify DirectControl daemon processes requests sequentially. For example: adclient.clients.threads: 4

If this parameter is not defined in the configuration file, its default value is 4 threads.

For high load servers please use values in the range 50-200.

adclient.clients.threads.max:
This configuration parameter specifies the maximum number of threads the Centrify DirectControl Agent will allocate for processing client requests.

This parameter value should be greater than or equal to the number of pre-allocated threads specified by the adclient.clients.threads parameter.  The default value is 20 threads.  For example:
adclient.clients.threads.max: 20

For high load servers please use values in the range 250-1250

adclient.use.all.cpus:
This configuration parameter specifies whether to use all the CPU's on the system or not.
The parameter value is set to true to use all the CPU's on the system or it can be set to false otherwise.
For example: adclient.use.all.cpus: false

As of the 4.3.0 agent version, the default value for this parameter is true.

For high servers which are multi processor, set this parameter to true

Since threads are allocated at agent starts up, If you modify any of the above parameters you must restart Centrify agent ;

To restart Centrify agent, adclient
# /usr/share/centrifydc/bin/centrifydc restart

Config Guide for Reference :
https://docs.centrify.com/en/css/2017.2/centrify-unix-config-guide.pdf

 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-3925: How to add Centrify parameter to a group policy articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7586: High CPU usage after 30 minutes after installing or upgrading to Suite 2016.1 (5.3.1) articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? article[Labs] Securing Windows Servers with Centrify Infrastructure Service - Enrollment, Settings and Sets articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-4011: High CPU consumption after a system with adclient is joined to a classic zone articleKB-2045: sudo hangs in autozone and adclient takes high CPU on RHEL/CentOS 6.4 servers