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
Rather than locking your type buffer, consider implementing a Load-Link Store-Conditional abstraction. Rather than worry about the state, just retry the whole chain if Store-Conditional fails.
The main benefit I see is it would potentially uncomplicate the code a lot. I'm not sure if it would be any faster, but it's conceivable it would.
The text was updated successfully, but these errors were encountered:
If you're interested, I know my friend Sandro Magi has written a LLSC abstraction in his Sasa NuGet package in the Sasa.Concurrency namespace. That would probably lower the bar for prototyping getting rid of the lock requirements.
@jzabroski Because the hash table has to be expended by doubling the size of the array and rebucketing the data, I don't think that technique works well. In any case, we only lock on writes, not on reads.
I should also mention that the implementation is intended to be suitable for use in the core library. Taking advantage of a higher-level library would undermine that.
Rather than locking your type buffer, consider implementing a Load-Link Store-Conditional abstraction. Rather than worry about the state, just retry the whole chain if Store-Conditional fails.
The main benefit I see is it would potentially uncomplicate the code a lot. I'm not sure if it would be any faster, but it's conceivable it would.
The text was updated successfully, but these errors were encountered: