|
|
|
COMMIT_DELAY <milliseconds | -1>
Controls the length of time in milliseconds after a given transaction completes that the transaction manager waits before flushing the transaction to disk. By waiting, more than one transaction (that is, the first one and all others that complete before the delay period expires) may be committed at the same time reducing disk-access overhead. On average, the longer the delay, the larger the number of transactions committed.
Note: Keep this delay in mind when setting a time limit for aborting transactions.
A value of "-1" disables this support.
Note: The best practice is to consider the type of storage device your transaction logs are sitting on.
Disable this support when using Solid State Disks (SSDs).
SSD use: COMMIT_DELAY -1
Enable it If you are running on a rotating hard disk.
HDD use: COMMIT_DELAY 1
Default:
Windows 2 ms.
Unix/Linux - This value defaults to 1 ms for best performance.
See Also
