You are correct, I meant to say 'worker process type' as opposed to 'web process type'.
So, the question then, is what would be the difference between a heroku scheduled command (which I currently am running, wakes up, does some work, etc) and a 'worker process' type? Does the latter need a job queue set up? Does it run constantly, checking that queue and consuming work items from it? On Monday, June 17, 2013 11:04:04 PM UTC-4, danneu wrote: > > Heroku cron jobs and workers are prorated like dynos. They run in their > own processes. So does booting into heroku bash or heroku console. > > Workers generally consume a queue. > > I'm not sure what you mean by "worker thread" though. Workers don't run in > a thread, and you can launch plain old threads whenever you want to in your > Clojure code. Heroku isn't going to bill you for threads. Perhaps I've > misunderstood. > > On Monday, June 17, 2013 7:27:21 PM UTC-5, Jonathon McKitrick wrote: >> >> How would you sum up the differences? Does the worker thread simply run >> all the time? Wouldn't that run up the dyno usage? > > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
