Persistence level determines how much process data and document content the engine writes to the database as a business process runs. Full persistence records state and data at every step, which multiplies database writes and lengthens run time, so IBM recommends the lowest persistence that still meets recovery and tracing needs, especially for high-volume processes. Cache properties control how often the system can reuse configuration, certificate and other reference data held in memory. When the caches are sized or set incorrectly, requests miss the cache and the system repeatedly reads the database or rebuilds objects, adding delay to every step. These two conditions are the ones associated with slow-running processes. A business process that lacks the right permission generally fails with an authorisation error rather than running slowly. Running in a particular queue, such as queue 3, is a normal scheduling arrangement and is not by itself a cause of delay. An exhausted connection pool is a separate capacity symptom that is investigated through Database Usage and the JDBC Monitor, and it is addressed by finding leaks rather than by changing process settings.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit