pedro

delayed_job

Ruby2010–2011

pedro / delayed_job

delayed_job

Database backed asynchronous priority queue -- Extracted from Shopify

Data & Databases

Explore on GitHub Read Hacker News discussions

6Distinct people

8Mentions

0Explicit recommenders

108GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Database backed asynchronous priority queue -- Extracted from Shopify

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month8 dated mentions

Observed mentions: 2010-08-27 05:20:45 UTC to 2011-05-26 10:19:33 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Aug 2010	2010-08-01 00:00:00 UTC	2010-09-01 00:00:00 UTC	2	2
Sep 2010	2010-09-01 00:00:00 UTC	2010-10-01 00:00:00 UTC	3	3
Oct 2010	2010-10-01 00:00:00 UTC	2010-11-01 00:00:00 UTC	0	0
Nov 2010	2010-11-01 00:00:00 UTC	2010-12-01 00:00:00 UTC	0	0
Dec 2010	2010-12-01 00:00:00 UTC	2011-01-01 00:00:00 UTC	1	1
Jan 2011	2011-01-01 00:00:00 UTC	2011-02-01 00:00:00 UTC	0	0
Feb 2011	2011-02-01 00:00:00 UTC	2011-03-01 00:00:00 UTC	0	0
Mar 2011	2011-03-01 00:00:00 UTC	2011-04-01 00:00:00 UTC	1	1
Apr 2011	2011-04-01 00:00:00 UTC	2011-05-01 00:00:00 UTC	0	0
May 2011	2011-05-01 00:00:00 UTC	2011-06-01 00:00:00 UTC	1	1

What Hacker News says

8 sources

hopeless·May 26, 2011

You've made this remark twice now. The fact is that Heroku have always been open this sort of scaling (and there's a fork of delayed_job which does autoscaling of workers on Heroku and... it's written by a Heroku employee. It's regularly mentioned on the mailing list too. https://github.com/pedro/delayed_job/tree/autoscaling

In HireFire - The Heroku Worker Manager

hopeless·Mar 28, 2011

I don't think that's true. There a fork of delayed_job which does autoscaling of workers on Heroku and... it's written by a Heroku employee. It's regularly mentioned on the mailing list too. https://github.com/pedro/delayed_job/tree/autoscaling

In Show HN: our Startup Weekend project - autoscale your Heroku dynos & workers

aaronbrethorst·Dec 16, 2010

Pedro's DJ fork[1] has worked quite well for me. What didn't go well with it for you? [1] https://github.com/pedro/delayed_job/tree/autoscaling

In Auto Scale your Heroku Apps with Hero Scale

siong1987·Sep 14, 2010

an addon might be overkilled. try the heroku gem. you can check out the example here: http://github.com/pedro/delayed_job/tree/autoscaling for worker, you might have to track the number of jobs in your queue. for dyno, you might have to track the number of requests you get within a time period.

In Heroku: Announcing the Add-on Provider Program

arfrank·Sep 14, 2010

They do for their background workers, but not the dynos. http://github.com/pedro/delayed_job/tree/autoscaling

In Tell HN: I accidentally ran up a $1000 Heroku bill

aaronbrethorst·Sep 14, 2010

One of Heroku's employees has a fork of delayed_job that handles autoscaling workers in the background. I use it in conjunction with several hourly cron jobs and it works like a charm. http://github.com/pedro/delayed_job/tree/autoscaling

In Tell HN: I accidentally ran up a $1000 Heroku bill

aarongough·Aug 27, 2010

Time consuming from a development stand-point, or billable-time standpoint? Switching to the auto-scaling version of delayed_job on heroku took me about 20 minutes and it has worked flawlessly ever since. The repo is here: http://github.com/pedro/delayed_job/tree/autoscaling

In How to Run Background Jobs on Heroku for Free

wuputah·Aug 27, 2010

Background workers only cost you money (5¢/hour) when they're running. It's prorated to the second. You can avoid running one constantly by using pedro's "autoscaling" branch, meaning you can run a few hours of background processing--which should equate to hundreds or thousands of jobs--every month for a few nickels. http://github.com/pedro/delayed_job/tree/autoscaling Pedro is a Heroku employee, so this use is totally fine by them, although the branch is not officially supported software. [I'm friends with a few guys there, but I don't work there.]

In How to Run Background Jobs on Heroku for Free