Using Chore Commit

ChoreCommit is a property of a chore that allows you to specify if the processes in a chore will be committed as a single transaction or if the processes in the chore are committed as multiple transactions.

A Chore executes a sequence of TurboIntegrator processes as a single Commit transaction. Any locks acquired by the first process are kept until the last process is complete. This means locks can be held for very long periods of time. ChoreCommit enables a Chore to optionally execute such that each TurboIntegrator process is committed as a transaction when the process is complete. Locks are then held only for the duration of a single process instead of for the length of the chore.

Chore Property

When setting up a chore, Chores can be identified as:

  • Single Commit Mode

    All processes are committed as a single transaction. This is legacy and default behavior.

  • Multiple Commit Mode

    Any processes that need to be committed do so as they are processed.

This property can be modified only when a Chore is inactive.