v0.9.0 brings major improvements for worker backends and logging:

  • Official Resque support
  • Corrected handling of failed jobs in Delayed Job
  • Better handling of jobs without a specified queue name
  • A "quiet mode" option if you find the gem too chatty in your logs
  • An improved "debug mode" when you need all the detail in your logs

The page you're reading right now. 😁 I haven't been great about tracking and sharing product updates, and this is my attempt to do better.

The official docs site is live! Prior to this, the only documentation was in the Heroku Dev Center, and it was insufficient. The new docs site will be the official canonical docs, frequently updated, and as extensive as possible.

A few bugfix releases were needed to address edge cases with Delayed Job and Que reporting.

Autoscaling Resque has been the top feature request ever since Sidekiq autoscaling was launched in 2019. Currently beta testing with several customers.

Request queue times can be skewed when Puma spends time waiting for large request bodies to be transferred by slow clients. That time does not indicate a capacity issue, and thus should not be factored into request queue time for autoscaling purposes.

Heroku does not allow free and hobby dynos to be scaled to more than one dyno, so Rails Autoscale had previously shown an error message if you attempted to enable autoscaling on these dynos. Some customers are autoscaling worker dynos down to zero dynos, though, and there's no reason you shouldn't be able to autoscale free/hobby dynos from 0-to-1. You can do that now.

Your Rails Autoscale dashboard now links to a "Dyno Usage" page. This page shows a daily breakdown of how many dyno-hours you've used, the cost of those dynos, and the money saved by autoscaling. Here's one crazy example.

Delayed Job and Que have joined Sidekiq in the job backends supported by worker autoscaling. πŸš€