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-7814:
git cherry-pick -x db86faec699aca67c02325bca22dcd5b913ddfed
GEODE-7814 has been marked as 'resolved in' 1.12.
Regards
EB
On Thu, Feb 27, 2020
+1
The change Juan has made corrects a problem introduced during membership
refactoring. Every cache operation message that's sent allocates several
objects that used to be held in statics but were moved into instance variables
at one point. Juan's change moves these back into static variable
+1
On Thu, Feb 27, 2020, 06:43 Owen Nichols wrote:
> +1
>
> On Thu, Feb 27, 2020 at 1:49 AM Ju@N wrote:
>
> > Hello devs,
> >
> > I'd like to include the fix for GEODE-7814 [1] in release 1.12.0.
> > The change prevents a huge amount of unnecessary allocation of objects
> > while sending/receiv
+1
On Thu, Feb 27, 2020 at 1:49 AM Ju@N wrote:
> Hello devs,
>
> I'd like to include the fix for GEODE-7814 [1] in release 1.12.0.
> The change prevents a huge amount of unnecessary allocation of objects
> while sending/receiving messages, improving the overall performance.
> The SHA is db86faec
Hello devs,
I'd like to include the fix for GEODE-7814 [1] in release 1.12.0.
The change prevents a huge amount of unnecessary allocation of objects
while sending/receiving messages, improving the overall performance.
The SHA is db86faec699aca67c02325bca22dcd5b913ddfed [2].
Best regards.
[1]: htt
