[SERVER-45162] RWCDefaults performance testing with continually changing defaults Created: 16/Dec/19  Updated: 28/Jan/20  Resolved: 28/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kevin Pulo
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-43724 RWCDefaults performance testing with ... Closed
Sprint: Sharding 2020-01-27, Sharding 2020-02-10
Participants:

 Description   

In order to measure the performance impact of changing the CWRWC defaults, the perf tests will run with an additional workload the continually sets the CWRWC defaults. This may be in the same perf test as above, or another one.



 Comments   
Comment by Kevin Pulo [ 28/Jan/20 ]

After offline discussion, it was determined that implementing this would not give any useful signal (especially as it does not correspond to any expected use-case), since it would just devolve into measuring the latency of the reading to get the RWC defaults document from the config.settings collection and/or config server.

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