[SERVER-30026] Perf test causal consistency Created: 06/Jul/17  Updated: 30/Oct/23  Resolved: 04/Dec/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.7.1

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: PM-221
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-30779 Investigate performance degradation i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Build 2017-07-10, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2017-12-18
Participants:

 Description   

Make sure that causal consistency performance impact expectations match the reality and quantify the coefficients.

reads secondary, auth is off: proportional to lag
reads secondary, auth is on: proportional to lag + constant overhead
reads primary, auth is off: no effect
reads primary, auth is on: constant overhead

also measure the performance when reads are from secondary and WaitForSecondaryBeforeNoopWriteMS is set to less then and greater then secondary lag. The latter case must demonstrate the step function as soon as noop writes will be generated.



 Comments   
Comment by Andy Schwerin [ 06/Jul/17 ]

I'd also like to see some of the mixed read-write workloads adjusted to do the reads from secondaries with causal consistency, in order to observe the impact of waiting for operation propagation.

Generated at Thu Feb 08 04:22:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.