couchbaselabs / couchbaselabs/ForestDB-Benchmark
transactional guarantees and recoverability
Open
- Dominant language
- C++
- Stars
- 33
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
What are the transactional guarantees enforced by each of these engines/configurations? I'm asking because:
- WiredTiger is configured for both checkpointing and the logging, which may or may not make sense,
- WiredTiger's checkpoint frequency is configured to match the LSM engines' compaction frequency, which doesn't make sense,
- WiredTiger is logging to the same disk partition as the data store, which will significantly affect performance.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.