While running performance tests (internally) using latest unstable releases having CommitMitigatedTieredMergePolicy we observed significant drop in performance (
The policy, although bad for performance, showed dramatic drop in churn created in data store size. So, clearly,
OAK-5192 did what it intended to do.
Opening this issue to factor in drop in performance and then set the default back to CommitMitigatedTieredMergePolicy.