sidekiq-throttled
sidekiq-throttled copied to clipboard
ixti
Concurrency and rate-limit throttling for Sidekiq
Every time heroku runs it's regular maintenance for redis I get a timeout issue. It used to run for a day or so and then go away but now the...
## What's the problem? The throttle is not being used in inherited classes. I've just noticed this by looking at the sidekiq web interface and realized that there were more...
I haven't had a chance to dig into it yet, but today, our throttled jobs stopped processing. Rather, the concurrency locks each had to time out before allowing another job...
If your `key_suffix` proc raises an error (e.g. its argument count doesn't match `perform`), then sidekiq-throttled [treats the worker as unthrottled](https://github.com/sensortower/sidekiq-throttled/blob/master/lib/sidekiq/throttled.rb#L89-L90). Having a message about the error would have saved...
In route `/sidekiq/queues` is show the column "Latency":  But in route `/sidekiq/enhanced-queues` not show:  tested in v0.15.0
Currently, using the `threshold` strategy, the throttling is based on when the job is picked up by the worker. It doesn't take into consideration whether the job is actually done....
Jobs do not seem to be throttled. Setting concurrency to `limit: 10` but moving all jobs to `busy`.
Hi! Thanks for writing and maintaining this gem. 🙏 It seemed like problems/questions for this repo should be posted as an issue here. If that's not true, please let me...
Hey folks, I know about using `sidekiq_throttle_as` to let multiple workers use the same throttling pool. I also know about dynamic throttling by using the `key_suffix`. Now I wonder if...
We have several workers in our default queue and one of them is throttled to one: ```ruby sidekiq_throttle(concurrency: { limit: 1 }) ``` when there are jobs queued with that...
