A Resque plugin which allows you to create dedicated queues for jobs that use rate-limited APIs. These queues will pause when one of the jobs hits a rate limit, and unpause after a suitable time period. The rate-limited queue can be used directly, and just requires catching the rate limit exception and pausing the queue. There are also additional queues provided that already include the pause/retry logic for Twitter, AngelList and Evernote; these allow you to support rate-limited APIs with minimal changes.

The plugin is designed for sequential running of different jobs in the same queue across multiple queues. Specifically meant for running a variety of long-running background tasks scheduled ahead of time using something like reque-scheduler. May not be suitable for large scale operations.

Allowing Resque to handle queues accross multiple Redis instances

Remotely enqueueing and dequeueing jobs across Redis namespaces should be simpler. BJ Neilsen laid a solid foundation for this gem, which is forked off of his gem resque-remote. That said, these two gems provide a different set of methods for remote enqueueing and dequeueing. If all you need is remote enqueueing within the same namespace, use resque-remote.

Usually Resque workers work on queues in the given order (if there is something in the first, work it, otherwise if the there is something in the second, work on it, and so on). This plugin randomizes the order of the queues based on weights, so that a given queue will be the first queue to try based on a probability weight. Given queues A, B, C, D and weights 4, 3, 2, 1, repsectively, A will be first 40% of the time, B 30%, C 20%, and D 10%. In addition, when B is first, A will be second 4/7ths of the time (4 / [4+2+1]), and so on. The project is inspired by resque-fairly, which unfortunately mathematically does not give you this control over the weights.

A Resque plugin. Implements an approximation of DelayedJob's send_later on resque. Has a little more ease-of-use and features than the example provided with Resque.

Adds support for serializable arguments in a Resque job. Serializable arguments can be passed to a Resque job via a Hash containing a :serialize key. If such arguments are found, they will be deserialized before calling the job's perform method

Ensures that only one Resque job with unique arguments is running at a time.

Declare resque queues serial and jobs in that queue will be run in serial mode

Integration of resque with resque-progress and resque-lock

A Resque failure backend for http://squash.io

A Resque gem for executing batches of jobs in stages. All jobs in a stage must complete before any job in the next stage is started allowing you to be sure that jobs are not executed out of sequence.

This will stagger your resque jobs over a configurable duration rather then enqueueing them all together

Start and manage multiple resque workers.

resque-state is an extension to the resque queue system that provides simple trackable jobs. It provides a Resque::Plugins::State::Hash class which can set/get the statuses of jobs and a Resque::Plugins::State class that, when included, provides easily trackable/killable/pausable jobs.

If you want to graph the workload created by your different Resque jobs, extend them with this plugin and use the data generated to know exactly the amount of jobs executed.

Resque plugin that pushes the job statistics to statsd

Swapping tool for Resque server on runtime.

Adds an arbitrary tab to resque-web which goes wherever you want

Helper for listing and viewing resque tasks at their various stages