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
The documentation indicates a lower value indicates more priority, which is incorrect according to implementation.
Items are added to a sorted set using the following formula, where priority defaults to 0:
score=priority- (now/10000000000)
Using current unix time stamps means typically items are scored with negative numbers like -0.1383766174 and getting smaller. Items are popped off using ZREVRANGE, which sorts from largest to smallest. If we set a negative priority, the item will not be fetched until the queue is empty, given that even a priority of -1 will make it considerably smaller than the default values.
The text was updated successfully, but these errors were encountered:
The documentation indicates a lower value indicates more priority, which is incorrect according to implementation.
Items are added to a sorted set using the following formula, where priority defaults to 0:
Using current unix time stamps means typically items are scored with negative numbers like
-0.1383766174
and getting smaller. Items are popped off using ZREVRANGE, which sorts from largest to smallest. If we set a negative priority, the item will not be fetched until the queue is empty, given that even a priority of -1 will make it considerably smaller than the default values.The text was updated successfully, but these errors were encountered: