On 08/02/2011 14:12, Simon Nash wrote:
Actually in its first incarnation the "force PBR override" setting was a
global flag that applied to the whole runtime, was set on by default,
and was poorly documented. (Hard to believe, I know.) After some
lobbying from myself the default was changed to off and the documentation
was improved, but people still saw it as a "go faster" flag and turned it
on when they shouldn't have done. Eventually it was made more granular
instead of a global thing and that helped some more. But the lessons
I learned were that 1) users experiencing performance problems will reach
for any magic go-faster switch and ignore all health warnings, and 2)
when it doesn't work they'll report it as a runtime bug.
Simon
Folks,
I think the nasty feature here is that IF the Java code on either side does the "wrong thing" and is
not clean wrt PBR, the bugs that result may be intermittent and somewhat hard to diagnose, since
they may well involve race conditions.
Yours, Mike.
