There appears to be consensus that this is a critical fix. The following commit has been brought into release/1.12 as the critical fix for GEODE-7820:
git cherry-pick -x ca7ccbce73d436005fe027f31ee910ee9beeb769 GEODE-7820 has been marked as 'resolved in' 1.12. Regards EB On Fri, Feb 28, 2020 at 7:51 AM Donal Evans <doev...@pivotal.io> wrote: > +1 > > On Fri, Feb 28, 2020 at 7:40 AM Owen Nichols <onich...@pivotal.io> wrote: > > > +1 > > > > On Fri, Feb 28, 2020 at 7:38 AM Udo Kohlmeyer <u...@apache.com> wrote: > > > > > +1, Keep the improvements coming... > > > > > > On 2/28/20 3:48 AM, Ju@N wrote: > > > > Hello devs, > > > > > > > > I'd like to include the fix for GEODE-7820 [1] in release 1.12.0. > > > > The change avoid unnecessary transformations between java collections > > and > > > > primitive arrays for every message sent within a Geode cluster (see > the > > > > Geode tickets for further details). > > > > The SHA is ca7ccbce73d436005fe027f31ee910ee9beeb769 [2]. > > > > My apologies for keep asking to merge changes into an already cut > > > release, > > > > we found a performance degradation (around 7%) within our internal > > > testings > > > > and we're trying to solve it step by step before version 1.12 is > > released > > > > (we are 3% away from the baseline, Geode 1.10, right now). > > > > Best regards. > > > > > > > > [1]: https://issues.apache.org/jira/browse/GEODE-7820 > > > > [2]: > > > > > > > > > > https://github.com/apache/geode/commit/ca7ccbce73d436005fe027f31ee910ee9beeb769 > > > > > > > > > >
