Modify the Maximum Database Operations per Transaction and the Maximum Instructions per Transaction parameter values to improve Instruction Sheet Interpreter activity.
For information about setting these parameters, see Setting performance parameters.
The following scenarios explain circumstances when either the Maximum Database Operations per Transaction or Maximum Instructions per Transaction parameter can be used to improve performance:
Description | Consider the following modification |
---|---|
Workflow maps that execute in the isolated region contain 750 - 1000 system instructions between user-defined instructions. | To maximize the availability of the ISI and other server resources, decrease the value of the Maximum Instructions per Transaction parameter. |
Description | Consider the following modification |
---|---|
The InstructionSheetInterpreter system queue is filling up. | Increase the value of the Maximum Instructions per
Transaction parameter. You can access the InstructionSheetInterpreter system queue through vwtool, APIs, or the administration console. |
Description | Consider the following modification |
---|---|
The size of the database audit trail has been exceeded, preventing further database activity. | Decrease the value of the Maximum
Database Operations Per Transaction parameter. See the database vendor documentation for information about optimizing or increasing the amount of space that is available for the database audit trail. |
Description | Consider the following modification |
---|---|
The amount of time between one-step processor dispatching a work item and the next step processor finding and locking that work item is excessive. | Decrease both parameter values. |