Understanding CPU binding
BIRT iHub System supports CPU binding on a machine with an appropriate CPU‑based license. CPU binding restricts a process or processes to run on a subset of CPU cores. If you bind the BIRT iHub System to a subset of CPU cores, only those CPU cores count toward the total number of licensed CPU cores. The CPU limit in the license file applies to all CPU cores for all machines in the cluster. Depending on the operating system and specific system command, you can restrict other processes from running on the processor to which you bind a process.
You can bind BIRT iHub processes to a specific set of processors on a machine that runs a Windows or Linux operating system. The default configuration does not bind BIRT iHub to a set of processors. In the default configuration, all processors on a BIRT iHub machine count toward the maximum number of licensed CPU cores.
To bind BIRT iHub to a set of processors, bind the iHub Daemon (ihubd) to the processors. ihubd starts all BIRT iHub processes. The processes inherit the binding from ihubd.
In a cluster, BIRT iHub counts only the processors on nodes that join the cluster and run the ihubc process. An ihubc process runs when a node is online. BIRT iHub counts the number of processors on a machine when the first ihubc process starts.
This section contains information on the following topics:
*Configuring CPU binding on Windows
*Configuring CPU binding on Linux
*Checking BIRT iHub bound processors
*Configuring e-mail for CPU license problems