In debugging, I noticed the fill rate isn't relevant if we're only assessing it after we've ticked into a new bucket. At that point, the full allocation of the bucket should be available for usage (as is for the first tick).
This doesn't have the effect of spreading out traffic evenly over the bucket.
This pull request has been automatically locked since there has not
been any recent activity after it was closed. Please open a new
issue for related bugs.
Fixes #29
In debugging, I noticed the fill rate isn't relevant if we're only assessing it after we've ticked into a new bucket. At that point, the full allocation of the bucket should be available for usage (as is for the first tick).
This doesn't have the effect of spreading out traffic evenly over the bucket.