Tuning Properties for Write-Behind Strategy

Tuning properties for write-behind strategy are used with the Coherence cache provider.

With write-behind strategy, sequential operations are used by default, instead of parallel operations (that is Agent.agentClassName.enableParallelOps=false).

There are no tuning properties for write behind and TIBCO BusinessEvents DataGrid. The following properties are used with the Coherence cache provider:

Cache service thread tuning
 Uses the following cluster-wide property:
tangosol.coherence.distributed.threads
Specifies the number of Coherence daemon threads used by the distributed cache service (per processing unit). If zero, all relevant tasks are performed on the service thread. For reference see TIBCO BusinessEvents Configuration Guide.
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 see TIBCO BusinessEvents Configuration Guide.