Skip to content

Conversation

@onomated
Copy link

No description provided.

msaffitz and others added 8 commits November 15, 2014 16:28
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.
The chunk_keys method is frequently used and relies on Redis's
keys operator, which is costly for instances with large numbers
of keys.  This instead relies on a Redis set to track chunks,
and significantly improves performance.
In testing large bitmaps saw a ~50x increase in speed
by pipelining operations.
Updates readme to use github markdown :)
msaffitz and others added 5 commits July 29, 2016 06:27
The chunk_keys method is frequently used and relies on Redis's
keys operator, which is costly for instances with large numbers
of keys.  This instead relies on a Redis set to track chunks,
and significantly improves performance.
Updates readme to use github markdown :)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants