On Mar 8, 2012, at 4:04 PM, Jack Royal-Gordon wrote: > Followup questions relating to question #2: > > 2.1) In the scenario addressed in question 2 below, would the two tasks run > in the same dyno, or does Heroku spin up another dyno for the second task? I > thought I had read that the scheduled task would allocate dynos from the pool > of dynos allocated for web and worker processes -- are you saying that > scheduled jobs always result in additional dynos being spun up?
Every time a task is run, a new dyno is spun up. At least for Cedar apps. > 2.2) Besides the obvious performance issues of the two > simultaneously-scheduled tasks competing for access to the database (and the > possible locking deadlocks that could occur), should I expect to see > performance issues with two scheduled tasks running simultaneously (e.g. will > the two scheduled tasks be competing for CPU cycles as though they were > running in the same dyno)? Each task gets their own isolated dyno, so separate memory, cpu, ephemeral filesystem, etc. They'll share any add-ons and databases, of course. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
