Home/ Questions/Q 8294129
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T14:05:50+00:00

Ok, so this is probably evil, however.. here’s the question! I want to run

  • 0

Ok, so this is probably evil, however.. here’s the question! I want to run a pretty lightweight app on a shared environment (site5). Ideally I would like to use delayed_job for the ease of queueing the mails (~200+ every so often). However, being a shared environment they don’t want background processes running all the time (fair enough).

So, my plan, such as it is, is to queue the mails using delayed job, and then every hour or something, spin up a cron job, send a few emails (10 or something small) and then kill the process. And repeat.

Q) Is there a rake jobs:works:1 equivalent task it’d be easy to setup? – pointer would be handy.

I’m quite open to “this is a terrible idea, don’t even go there” being the answer.. in which case I might look at another queuing strategy… (or heroku hire-fire perhaps..)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can get delayed job to process only a certain number of jobs by doing:

    Delayed::Worker.new.work_off(10)

    You could fire a script to do that from cron or use “rails runner”:

    rails runner -e production 'Delayed::Worker.new.work_off(10)'

    I guess the main issue on whether it is a good idea or not is working out what small value is actually high enough to make sure you process all your jobs in a reasonable time-frame. Also, you’ve got the overhead of firing up the rails environment every time you want to process, or even check whether you should process, any jobs. That might cause problems in a shared environment if they are particularly strict on spikes of memory or CPU usage.

    • 0