Skip to content

Strong vs Weak CAS in main push/pop loops #12

Description

@Saalvage

Idea behind current usage of weak CAS is that failure there still indicates contention which can be avoided by claiming a new block.
However, especially for read windows with unavoidable contention this may result in unnecessary block re-claims.

In general, maybe CAS should simply be reattempted before new block claim (esp. in pop case)?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions