> > I don't really mind the sluggish spin up time. What I do mind is > having slug compilation occasionally take 4+ hours instead of the > normal 3 minutes. That means I can't show my boss the current state of >
Slug compile should never take that long. It sounds like a bug - we have noticed a few stale lock files on compiles. We're digging in to see what's going on over the next few weeks on this particular area. For the sake of clarity (and a future docs page I'll put up): h1. When do you idle my app? Only dynos are idled, not workers. If you have only 1 free dyno, your app will be spun down after a period of inactivity. This period is variable depending on demand on the platform, but is never less than 20 minutes or more than 1 hour. No other resources are different. Git push, slug compilation, etc are all identical. Increasing your dyno to >1 will prevent your app from idling out. Note: other resources (workers, add-ons) do not effect dyno idling at this time. If you have 1 dyno + 10 workers, your dyno will still idle out after a period of inactivity. We never idle out workers. What other questions do you guys have on the area that I should include? Oren -- 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.
