Group Delay (-groupdelay)
- Last Updated: August 23, 2021
- 1 minute read
- OpenEdge
- Version 12.2
- Documentation
| Operating system and syntax | UNIX / Windows |
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| DBS | 32,766 | 0 | 0 | 10 |
- n
- The number of milliseconds a transaction waits before committing.
Use Group Delay (-groupdelay) to increase
performance when Delayed BI File Write (-Mf) is set to
zero. When the Group Delay is set greater than zero (0), the database engine uses a
technique known as Group Commit. When using Group Commit, a transaction spools its end note
to the BI buffer and waits a short time until the buffer becomes full and is written to
disk, or waits for other transactions to end and store their end notes in the BI buffer so
that several transactions are committed by the same synchronous write. In this manner, Group
Commit benefits overall performance, although each individual transaction might take
slightly longer.
The Group Delay (-groupdelay) parameter
may be modified while your database is online using PROMON or through the _DbParams VST.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.