Tuning the performance of instance migration
You can improve the performance of migrating process instances by adjusting configuration options for migrating instances.
About this task
Performance depends on the number of instances in the
process, the number of tasks in those instances, and the size of the
execution context. To improve the performance of migrating instances
from one snapshot to another snapshot, you can configure the migration
process. The configuration options determine which tasks to migrate,
set the number of threads in the pool, and whether to defer updating
the execution context of the tasks. The 99Local.xml file
contains the default values for these configuration options:
<server>
<instance-migration>
<thread-pool-size>5</thread-pool-size>
<migrate-tasks>skip-closed<migrate-tasks>
<defer-ec>false</defer-ec>
</instance-migration>
</server>
Procedure
Example
The following example shows thread-pool-size set
to 10 and defer-ec set to true, while migrate-tasks is
left as the default, skip-closed.
<server>
<instance-migration merge="mergeChildren">
<thread-pool-size merge="replace">10</thread-pool-size>
<defer-ec merge="replace">true</defer-ec>
</instance-migration>
</server>
The following example shows thread-pool-size set
to 10 and migrate-tasks set to all, while defer-ec is
left as the default, false.
<server>
<instance-migration merge="mergeChildren">
<thread-pool-size merge="replace">10</thread-pool-size>
<migrate-tasks merge="replace">all</migrate-tasks>
</instance-migration>
</server>
The following example shows overriding
all three values.
<server>
<instance-migration merge="mergeChildren">
<thread-pool-size merge="replace">8</thread-pool-size>
<migrate-tasks merge="replace">none</migrate-tasks>
<defer-ec merge="replace">true</defer-ec>
</instance-migration>
</server>