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
I noticed that BaseMpscLinkedArrayQueue and MpscBlockingConsumerQueue use soElement(buffer, offset, null) but MpscArrayQueue uses spElement(buffer, offset, null), and could not think of a reason for the difference.
I know for correctness plain is fine so assumed if the so is intentional it must be GC-related, but then why the inconsistency?
The text was updated successfully, but these errors were encountered:
I know for correctness plain is fine so assumed if the so is intentional it must be GC-related, but then why the inconsistency?
IIRC both the queues make use of consumerIndex release on producer side to wide the producerLimit so they could both make use of spElement on consumer side without breaking anything IMO.
I don't see particular reasons for this difference, sometime it just happens: performance wise there is a very small difference (if none TBH) between the 2s and I think is a change that can be proposed with no fear 👍
I noticed that
BaseMpscLinkedArrayQueue
andMpscBlockingConsumerQueue
usesoElement(buffer, offset, null)
butMpscArrayQueue
usesspElement(buffer, offset, null)
, and could not think of a reason for the difference.I know for correctness plain is fine so assumed if the
so
is intentional it must be GC-related, but then why the inconsistency?The text was updated successfully, but these errors were encountered: