CARVIEW |
Every repository with this icon (

Every repository with this icon (

Fork of tobi/delayed_job | |
Description: | Database based asynchronously priority queue system -- Extracted from Shopify edit |
Homepage: | https://www.shopify.com edit |
Public Clone URL: |
git://github.com/Shopify/delayed_job.git
Give this clone URL to anyone.
git clone git://github.com/Shopify/delayed_job.git
|
Your Clone URL: |
Use this clone URL yourself.
git clone git@github.com:Shopify/delayed_job.git
|
name | age | message | |
---|---|---|---|
![]() |
MIT-LICENSE | Sun Feb 17 13:01:35 -0800 2008 | Initial extraction [tobi] |
![]() |
README.textile | Sun Mar 23 07:15:26 -0700 2008 | More formatting updates for readme [tobi] |
![]() |
init.rb | Sun Feb 17 13:01:35 -0800 2008 | Initial extraction [tobi] |
![]() |
lib/ | Sun Mar 23 07:04:09 -0700 2008 | Removed the global lock. Jobs can now processed... [tobi] |
![]() |
spec/ | Mon Mar 24 09:01:03 -0700 2008 | Don't save jobs with empty handlers [tobi] |
![]() |
tasks/ | Sun Mar 23 07:08:18 -0700 2008 | Small corrections for the included rake task [tobi] |
Delayed::Job
Delated_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background.
It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks. Amongst those tasks are:
- sending massive newsletters
- image resizing
- http downloads
- updating smart collections
- updating solr, our search server, after product changes
- batch imports
- spam checks
Changes
- 1.5 Job runners can now be run in parallel. Two new database columns are needed: locked_until and locked_by. This allows us to use pessimistic locking, which enables us to run as many worker processes as we need to speed up queue processing.
- 1.0 Initial release
Setup
The library evolves around a delayed_jobs table which looks as follows:
create_table :delayed_jobs, :force => true do |table| table.integer :priority, :default => 0 table.integer :attempts, :default => 0 table.text :handler table.string :last_error table.datetime :run_at table.datetime :locked_until table.string :locked_by table.timestamps endUsage
Jobs are simple ruby objects with a method called perform. Any object which responds to perform can be stuffed into the jobs table.
Job objects are serialized to yaml so that they can later be resurrected by the job runner.
There is also a second way to get jobs in the queue: send_later.
BatchImporter.new(Shop.find(1)).send_later(:import_massive_csv, massive_csv)This will simply create a Delayed::PerformableMethod job in the jobs table which serializes all the parameters you pass to it. There are some special smarts for active record objects
which are stored as their text representation and loaded from the database fresh when the job is actually run later.
Running the tasks
You can invoke rake jobs:work
which will start working off jobs. You can cancel the rake task by CTRL-C
.
At Shopify we run the the tasks from a simple script/job_runner which is being invoked by runnit:
#!/usr/bin/env ruby
require File.dirname(__FILE__) + '/../config/environment'
SLEEP = 5
trap('TERM') { puts 'Exiting...'; $exit = true }
trap('INT') { puts 'Exiting...'; $exit = true }
puts "*** Staring job worker #{Delayed::Job.worker_name}"
begin
loop do
result = nil
realtime = Benchmark.realtime do
result = Delayed::Job.work_off
end
count = result.sum
break if $exit
if count.zero?
sleep(SLEEP)
puts 'Waiting for more jobs...'
else
status = "#{count} jobs processed at %.4f j/s, %d failed ..." % [count / realtime, result.last]
RAILS_DEFAULT_LOGGER.info status
puts status
end
break if $exit
end
ensure
Delayed::Job.clear_locks!
end