Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't use transactions (multi) for bitops #4

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Don't use transactions (multi) for bitops #4

wants to merge 2 commits into from

Commits on Nov 16, 2014

  1. Don't use transactions (multi) for bitops 

    If you use a bitop against a frequently changing bitmap,
the multi can be cancelled because the underlying key tracked
by watch will change and invalidate the transaction.  The
biota will then return invalid results (0).  This removes the
transaction block.  Unknown if this is dangerous if the bitmap is
in the process of being copied.  Causes bitops to not be strongly
consistent.
    @msaffitz
    msaffitz committed Nov 16, 2014
    Configuration menu
    Copy the full SHA
    ab5cfa5 View commit details
    Browse the repository at this point in the history

  2. Pipeline bit operations to increase speed. 

    In testing large bitmaps saw a ~50x increase in speed
by pipelining operations.
    @msaffitz
    msaffitz committed Nov 16, 2014
    Configuration menu
    Copy the full SHA
    362837d View commit details
    Browse the repository at this point in the history