-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Statistics
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - Q3+ Backlog
-
5
Currently the solution for solving races for stats with max semantic is to use
`WT_DEFINE_STATS_MAX_ATOMIC_UPDATE` that uses atomic loads + stores to update the value. That may be better from a performance perspective but can result in lower values overwriting higher ones. We assume this is acceptable since stats are allowed to be fuzzy in exchange for reduced performance overhead.
The scope of this ticket is to use CAS to update max statistics when they all start to use the macro created for this purpose and check whether it brings any perf degradations.