Sunday, June 30, 2013
Hi
I want to use Sidekiq to run some jobs in the background. The jobs will be created by the whenever gem (or similar) which creates a Sidekiq worker at a specific time. This worker will in turn create a few hundred Sidekiq jobs.
So, I'm using Heroku and wonder if I need to use a separate worker dyno for these jobs? Or can I use, for example, Unicorn to run Sidekiq "inside" my one web dyno?
I read something about it here: https://coderwall.com/p/fprnhg
But is it a good idea?
If it is not appropriate do it this way, can I spin up a separate worker when I need to? Perhaps I will create these jobs once a week. It would be cool to create a worker -> finish all jobs -> kill worker. Possible?
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/fb04a82a-ae34-43c2-b6b4-7edc1e7e02fb%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment