delayed-job

Is it possible to run delayed jobs on Heroku for free? I'm trying to use delayed_job_active_record on Heroku. However, it requires a worker dyno and it would cost money if I turned this dyno on for full time. I thought using Unicorn and making its workers run delayed jobs instead of the Heroku worker, would cost nothing, while successfully running all the jobs. However, Unicorn workers do not seem to start "working" automatically. I have the following in my Procfile . web: bundle exec unicorn -p $PORT -c ./config/unicorn.rb worker: bundle exec rake jobs:work and the following in my unicorn.rb

Just wondering how to test that actionmailer requests are actually sent to the delayed_job que in rspec. I would have assumed it was quite simple, but my delayed_job queue doesn't seem to be incrementing. Code below: Controller: def create @contact = Contact.new(params[:contact]) if @contact.save contactmailer = ContactMailer contactmailer.delay.contact_message(@contact) redirect_to(contacts_url) else render :action => "new" end Spec: it "queues mail when a contact is created" do expectedcount = Delayed::Job.count + 1 Contact.stub(:new).with(mock_contact()) { mock_contact(:save => true) } post

For some reason, Delayed::Job's has decided to queue up but not excecute anything even though I've restarted it several times, even kill -9'd it and restarted it. It won't run any jobs. Can I , in /console, specify a specific job and tell it to work? Ex:.. Delayed::Job.find(x).run answering how to run specific job from console: Delayed::Job.find(x).invoke_job but you must remember that it won't run any other things like destroying job that was done or so on. just running the job/task. David Tuite You can also do it like this: Delayed::Worker.new.run( Delayed::Job.find(x) ) On Heroku I had a

I have a Rails app on a free tier on Heroku and it recently started getting some users. One of the events in my app involves querying another API and can take up to 10 seconds to finish. How do I make sure other users who visit a simple page at the same time (as another user's API event) don't need to wait 10 seconds for their page to load? Do I need to pay for more Dynos? Is this something that can be solved with the delayed_job gem? Would another host (like AppFog or OpenShift) be able to handle simultaneous requests faster? Update: This question suggest manually handling threads instead of

I am performing some job with Resque-worker (5 workers). Now, when this job is completed/done I want to trigger another worker which processes the data previous worker stored in db. What would be the most appropriate method of doing this? I'm not sure if this is of any help, but have you had a look at the resque-status gem? That way you can track a given jobs' status, to see when it is completed. But I'm affraid there are no auto-trigger functionality, to start new workers. 来源： https://stackoverflow.com/questions/8383259/knowing-when-resque-worker-had-completed-job

Objective: To save successfully completed jobs Methods used Have looked at this answer which tells how to save completed jobs and this answer which suggests to create a plugin which will be executed after one of lifecycle events. Problem There are following lifecycle events, and applicable arguments as present in code : :enqueue => [:job], :execute => [:worker], :loop => [:worker], :perform => [:worker, :job], :error => [:worker, :job], :failure => [:worker, :job], :invoke_job => [:job] I had expected there will be some event corresponding to success, I am not getting which one will be

SomeController#update (RestClient::ResourceNotFound) "Resource Not Found" I'm receiving this error (where previously I was not) while trying to enqueue delayed jobs using the autoscale branch of DelayedJob. This does not occur with a none autoscale branch but I'm at a loss to pinpoint what the problem is. If anyone is experiencing the same or can point me toward a likely cause I'd be grateful for advice. Just a guess... Is it possible the ResourceNotFound is occurring because the heroku gem cannot find your app when making the API requests to auto-scale? Try using the heroku gem outside your