Also, Ritesh Agarwal when running my latency and throughput tests, the metrics will perform better at the beginning of the tests. 1000 docs will show better latency. If you run longer tests, the realtime throughout and latency will drop further until it reaches a limit.

For a 4 nodes cluster, replica = 2
Majority = (2 + 1)/2 + 1(Active) = 2 nodes

1. DurabilityLevel.NONE == PersistTo.NONE, ReplicateTo.NONE
> according to your comment above they are not the same, how?

2. DurabilityLevel.MAJORITY == PersistTo.NONE, ReplicateTo.ONE(Active + 1 Replica)

3. DurabilityLevel.PERSIST_TO_MAJORITY(Does it includes ACTIVE for persistence or any majority nodes is fine?) == PersistTo.TWO(Any two), ReplicateTo.ONE(Active + 1 Replica)

OR

DurabilityLevel.PERSIST_TO_MAJORITY = PersistTo.ACTIVE + PersistTo.ONE, ReplicateTo.ONE(Active + 1 Replica)

4. DurabilityLevel.MAJORITY_AND_PERSIST_ON_MASTER == PersistTo.ACTIVE, ReplicateTo.ONE(Active + 1 Replica)

Dave Rigby: Can you please confirm on this?

1. DurabilityLevel.NONE == PersistTo.NONE, ReplicateTo.NONE
> according to your comment above they are not the same, how?

They should be both logically the same and physically encoded on the wire the same, so there should be no difference between them. Any differences in numbers we see should be investigated as that's not expected. There was some suggestion that in the test above, given we run one one durability setting before the other there could be some difference in JVM warmup / cluster warmup but that's not yet clear.

DurabilityLevel.PERSIST_TO_MAJORITY = PersistTo.ACTIVE + PersistTo.ONE, ReplicateTo.ONE(Active + 1 Replica)

This one. All the Sync Replication levels must always include the current active node as one of the "majority" set of nodes.

Ritesh Agarwal

Do you still see the issue in your tests?  Thanks.

Closing the defect based on Korri's performance tests results data in excel sheet.