You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously we were initializing the pipelineEnabler on a copy of the
txnWriteBuffer that would later be overwritten. As a result, we were
never re-enabling pipelining after a mid-transaction flush. This is OK
from a correctness perspective since this was only intended as a
potential performance improvement for some workloads under buffered
writes.
There is a potentially strong argument that we shouldn't do this at all
and that if someone sees a regression of their workload under buffered
writes they should turn it off rather than relying on this fallback.
Epic: None
Release note: None
0 commit comments