2. Under # POLICY CONFIGURATION - ALL Policies, locate the MaxThreads
property and change the value to the value you determine is best for your level
of processing.
Note: Setting the MaxThreads value higher does not guarantee that you will
have faster processing. Depending on your system resources, setting the
MaxThreads value too high may degrade performance. Set MaxThreads
according to your processing volumes in relation to your number of CPUs.
3. Under # QUEUE CONFIGURATION, Queue # - ALL Policies, where # indicates the
queue number, locate the properties described in the following table and
change the values for each as appropriate. Complete this step for each queue
that you are using. For each property, # indicates the queue number, for
example, AE_ExecuteCycle.3 is the AE_ExecuteCycle property for the third
queue. Also, property values can be different for each queue.
Property Description
AE_ExecuteCycle.# Number of steps for a business process to complete prior to
returning to the queue. Higher values will accelerate
individual business process execution, while lower values
enables smoother multitasking. Interactive use favors a lower
number of steps, while batch processing favors a higher
number of steps.
AE_ExecuteCycleTime.# Maximum time period, in milliseconds, that a business process
can use a thread, for releasing it for use by another business
process. This value will override the value set for
AE_ExecuteCycle. This is intended to ensure that a series of
unusually slow steps do not tie up a thread completely.
QueueDepth.# Maximum number of business processes that can be in a
queue at a given time. Generally, this value should be left at
the default value of 10,000, unless you anticipate having more
that 10,000 business processes in a queue at the same time.
MaxPoolSize.# Maximum number of threads executed for a specific queue.
The MaxThreads value overrides the MaxPoolSize value if the
MaxPoolSize value is set higher than the MaxThreads value.
Note: Setting all the queues' MaxPoolSize parameters to the
maximum threads available does not mean you will have
faster processing. Depending on your system resources, setting
the MaxPoolSize value too high may cause the queues to back
up and degrade performance. A good place to start is 4 times
the number of your CPUs. Interactive use tends to favor more
threads, while batch or document processing tends to favor
less threads.
174 Sterling B2B Integrator: Performance Management
