One method of managing performance for MPF requests is to modify the number of threads that are used to process queued requests. Each thread processes a single MPF request.
When all threads are busy with requests, additional requests must remain in the queue until threads become available. A request may take a long time to execute, even if it is not consuming too many resources on the computer. For example, if a request issues a complex SQL query, the thread is unavailable for other processes until SQL completes the query.
If you have requests that require significant processing time but not extensive utilization of the central processing unit and memory, you can increase the number of threads. When you increase the number of threads, it can speed up the pace at which MPF processes queued requests.
For more information about modifying the number of threads used to process queued requests, see Administering queue managers and Change the number of threads used to process queued requests.
It is important to configure transaction log maintenance to achieve optimal performance for your environment. Moving transactions from the transaction log to the audit log too often can significantly impact processing times. Moving transactions to the audit log too infrequently can flood the transaction log.
You should enable schema validation only when testing new functionality. Leaving schema validation enabled when you go to a live production environment can result in siginficant performance problems.