Overview

Select candidate workloads for measuring the success of the conflict detection architecture, measure the prototype against the existing write path, and propose tentative performance goals.

Scope of Work

• Candidate workloads, e.g. TPC-C, hot-key contended transactions, YCSB, and random-key multi-document transactions (write amplification).
• Measure abort rate, commit latency, apply lag and throughput vs. the existing path. YCSB measurements can begin before detector integration.

Acceptance Criteria

• Workloads, results, and proposed tentative goals recorded on this ticket.

Technical Notes

• Prototype quality; not intended for commit to master.

Design Note Alignment

• Acceptance bar: the full jstest suite passes with featureFlagStagedWrites enabled, except for specific tests excluded with a documented reason tied to prototype scope.
• Measure the per-write hot-path overhead of staging with the flag on, and verify the flag-off path costs nothing.
• Measure conflict detector memory growth and floor advancement under a global flag.
• Design reference: src/mongo/db/txns/staged_writes_design.md (PR #66680).