![]() ![]() |
|
Help for Process Engine Administration | |
Search | Index | |
![]() |
|
![]() |
![]() |
![]() |
Other ways to improve performanceYou can improve the performance of your system by changing the event logging and statistics settings, by monitoring the use of exposed fields, and by balancing the system workload between Process Engines in a multi-server configuration. Event logging settingsCertain event logging options cause slight performance degradation. The overall degradation is about 5% on the server, with no noticeable degradation on the PC workstation. You can enable or disable logging for a specific event category in an isolated region through the Process Configuration Console. For more information, see the Process Configuration Console online help. Statistics settingsStatistics collection can have an effect on the overall performance of your system. You can enable or disable the collection of statistics in an isolated region, as well as configure how often statistical snapshots of the system are taken, and how often statistical information is written to the database tables. To enable or disable statistics collection Use the Process Configuration Console to enable or disable statistics collection for an isolated region. For more information on statistics collection, see the Process Configuration Console online help. To configure statistics collection Use the Process Configuration Console to define VWService-wide statistics settings. These statistics settings define how often statistical snapshots are taken of the system, as well as how often statistical information is written to the database tables. For more information, see the Process Configuration Console online help. Exposed fieldsExposing some system or data fields in a roster can have a degrading effect on performance. Fields that changes often (such as F_OperationId, F_Comments, or F_StepProcId) should never be exposed in a roster. Fields exposed in a roster should be very stable fields that do not change often. The reason is that rosters are only updated when a work item moves from server to server or when an exposed field changes. The degradation resulting from improperly exposed fields in a multi-server environment can be significant. If you are experiencing poor performance, look at the fields exposed in each roster, and review the frequency of updates for each exposed field. If you find an exposed field that is frequently updated, remove it and see if performance improves. Workload balancingYou can perform load balancing by moving a queue or workflow roster from one Process Engine to another in a multi-server configuration. For more information, see the Process Configuration Console online help
|
![]() |
|
![]() |
|