That 4.6% degradation is within our thresholds so it is possible this came in well before the first time it was detected.
Some context on the benchmark for those unfamiliar: P2pPartitionedPutLongBenchmark performs a fire hose of puts with Long key and Long value directly from each of the two servers. This results in a lot of little p2p messages being exchanged between the servers. Presumably 50% of the puts result in forward to the primary bucket plus the replication message for every put. This test can be susceptible to the smallest alteration in garbage production/collection, hot methods, locks, etc. This test is a very unlikely scenario in production. I am not sure that constitutes a blocking condition but is troubling. I will give a neutral vote on making it a blocker. > On Mar 12, 2021, at 11:19 AM, Donal Evans <doev...@vmware.com> wrote: > > After some investigation, it appears that a degradation has been introduced > that causes the P2pPartitionedPutLongBenchmark to fail at an increased rate. > Efforts are underway to narrow down the cause to a single commit, but the > degradation was definitely introduced in 1.14, so I believe this should be > considered a 1.14 release blocker: > https://issues.apache.org/jira/browse/GEODE-8950
