NCC: Natural Concurrency Control for Strictly Serializable Datastores by Avoiding the...
summary
NCC is a concretely implemented concurrency control that executes naturally ordered transactions lock-free with non-blocking execution and decoupled response management, uses client-side timestamp-based consistency checking, and adds response-timing control to eliminate a discovered timestamp-inversion pitfall. The system guarantees strict serializability with best-case one-round latency, reduces false aborts via asynchrony-aware timestamps and smart retry, and in OSDI evaluations outperforms existing strict solutions (orders-of-magnitude on many workloads, ≳2× throughput vs OCC) while matching weaker MVTO performance.
AI-written summary · about
chapters (11)
- 0:00NCC introduction and goals
- 2:15Strict serializability limits
- 3:41Natural consistency in workloads
- 4:50Three pillars of NCC
- 5:16Non-blocking server execution
- 8:09Client timestamp consistency
- 9:19Timestamp inversion pitfall
- 11:27Avoiding timestamp inversion
- 12:51System overview
- 13:34Implementation and results
- 14:59Summary
related talks
45mTransactions and Concurrency Control Patterns
01h 11mMVCC unmasked
11mUnifying Timestamp with Transaction Ordering for MVCC with Decentralized Scalar Timestamp
17mJust-Right Consistency
51mHigh-concurrency distributed snapshots
12mConcordia: Distributed Shared Memory with In-Network Cache Coherence
18mAvoiding Conflicts in Highly-Concurrent Applications
15mRethinking Safe Consistency in Distributed Object-Oriented Programming
