Mitigate rate limiter slow down due to rounding error #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use to_f instead of to_i to avoid slowing down the rate limiter
|
thanks @ryana also looks like there is an unrelated rspec version issue causing the build to fail i'll fix that |
seanxiesx
added a commit
that referenced
this pull request
Dec 30, 2014
Mitigate rate limiter slow down due to rounding error
|
pushed 0.0.8 to rubygems |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use
to_finstead ofto_ito avoid slowing down the rate limiter. Checkout this ticket I opened on the sidekiq-rate-limiter gem. Basically, usingto_iintroduces huge rounding errors (technically, afloor-ing error) that can significantly slow things down over time.