Parallel operations is only used with cache aside (defaults to false for write behind). It is an agent level property, so you can set it differently on each agent, depending on the needs. For reference documentation, see
Table 53, CDD Agent Classes Tab Inference Agent and Query Agent Properties in
TIBCO BusinessEvents Developer’s Guide.
Message Acknowledgment With both parallel and sequential operations, message acknowledgement and releasing locks (epilog actions) wait for the three post-RTC tasks to complete. Note the following exceptions:
Parallel Operations When the enableParallelOps property is set to
true, parallel operations are used. Parallel operations is shown in the diagram for this section. It uses multiple threads and queues for more efficient processing during the post-RTC phase.
Sequential Operations When the enableParallelOps property is set to
false, sequential operations are used. This means that all post-RTC phase operations are done on a single thread. Sequential operations ensures that the system waits to send a reply event confirming that some work has been done, until the result of the work can be seen in the cache.
Cache writer thread tuning One cache writer property is available. It is set at the agent class level:
(For the diagram legend, see Cache-Aside Options.) For backing store inserts and updates, one write-behind thread is used for each entity type. Deletes are performed by the distributed cache threads (configurable) and they are synchronously deleted from the database.
Cache service thread tuning Uses the following cluster-wide property:
Database writes batch size tuning When Coherence provides many updates, the backing store commits the writes to the database after each be.backingstore.commitSize batch size is reached. For reference documentation see
Table 46, CDD Cluster Tab Backing Store Properties in
TIBCO BusinessEvents Developer’s Guide.