Binding an Actuate process to a processor
If you bind the BIRT iHub PMD to a subset of CPUs on a machine, you can also bind the Factory, View, Integration, and Caching processes to a specific CPU. Under some conditions, binding an Actuate process to a specific CPU can enhance performance. Binding an Actuate process to a CPU has no affect on the CPU calculations BIRT iHub performs to determine the maximum number of licensed CPUs.
If you bind a process to a CPU, you must bind the CPU to both the BIRT iHub PMD and the process. BIRT iHub writes to the error log and stops the process if you bind a process to a CPU that you do not bind to the PMD.
To bind a BIRT iHub process to CPU processors, use the ProcessorAffinity element in the acserverconfig.xml file for BIRT iHub. List the IDs for the CPUs to which to bind a process as Item subelements in the following ProcessorAffinity elements:
To bind Factory processes, specify the CPU IDs in the ProcessorAffinity element within the ReportingService element.
To bind View processes, specify the CPU IDs in the ProcessorAffinity element within the ViewingService element.
To bind Integration processes, specify the CPU IDs in the ProcessorAffinity element within the IntegrationService element.
You must also ensure that you bind the specified CPUs to the PMD for the BIRT iHub machine. For example, on a four-CPU machine, the following ProcessorAffinity example binds View processes to CPU IDs 0 and 2:
<ViewingService
EnableViewingService="true"
<ProcessorAffinity>
<Item>0</Item>
<Item>2</Item>
</ProcessorAffinity>
/>