Add support for Covered Indexes
Use a new 'priority' attribute in each document. Sort by this priority attribute when pulling jobs from the queue. Priority is completely optional
…red indexes which became available in Mongo 1.8 (http://www.mongodb.org/display/DOCS/Retrieving+a+Subset+of+Fields#RetrievingaSubsetofFields-CoveredIndexes).
2) Change the run(), hasRunnable() and count() queries to include jobs with a null "when".
…ntion on high load queues, but it's still a good utility method to have around.
…anually sharded setup.
…atch and the new job.
…() call, which runs very slowly when the queue is being populated/drained at high rates. 2) Add place holder locked, locked_at, and batch fields for documents. 3) Add indexing suggestions in README
…ue so that if a job exists with the same parameters, nothing will be added. This is ideal for batchable idempotent operations.
…un currently. Fix environment loading so that it does not register a loader for every run() call.
…s then loaded automatically as static member variables of the Job class
…Job classes will automatically be loaded.
…to get some syntactic sugar around inserting jobs