PS-9822 Improve documentation on MyRocks variables (8.0) #517
Conversation
patrickbirch
changed the title
On branch ps-9822 modified: docs/variables.md
| Enabling `rocksdb_enable_pipelined_write` activates this feature. It is | ||
| especially useful in workloads with high concurrency or transaction phases | ||
| that generate bursts of write activity, such as the prepare step in | ||
| two-phase commit protocols. |
There was a problem hiding this comment.
Original text: beneficial in
a) workloads with multiple concurrent writers [and]
b) in scenarios like the prepare phase of a two-phase commit
"prepare phase" should stay because it's a proper name:
Two-Phase Commit (2PC) is a distributed algorithm used to ensure atomicity across multiple systems or databases in a transaction. It ensures that either all participants commit the transaction or none of them do, preventing data inconsistency.
Phase 1: Prepare (Voting Phase)
Phase 2: Commit (Decision Phase)
|
|
||
|
|
||
| RocksDB uses pipelined writes to increase throughput in workloads with | ||
| concurrent writers. When the Write-Ahead Log (WAL) is enabled, write |
There was a problem hiding this comment.
Original text: The pipelined write feature in RocksDB is designed to improve concurrent write throughput when the Write-Ahead Log (WAL) is enabled.
We lost info that The pipelined write feature works only if Write-Ahead Log (WAL) is enabled.
On branch ps-9822
modified: docs/variables.md