I suggest you ...

Process count overrides

We often have to 1) increase the worker process count if one of our queues gets backed up or 2) set the process count to zero for migrations. To accommodate this the scheduler should reset the process count only when the scheduled process count changes. So if we have 4 processes scheduled between 7am and 7pm and 2 processes scheduled between 7pm and 7am, at 7pm it should reset to 2 processes and at 7am it should reset to 4 workers. Any manual changes in process count should not be reset other than at those times. This is obviously ideal for our use case, but it may not be for everyone else, so we would appreciate any feedback on if others would find this useful or not.

Thanks for building this product, it is helping us save a signficant amount.

14 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Evan shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Mike commented  · 

        Only changing dynos at an hour when the setting changes in the schedule would be my preferred behavior also.

        I haven't tried to run maintenance mode with this yet, if it still scales each hour with maintenance:on it would be great to be able to have the scheduler skip any changes during that period.

      • Ari Pollak commented  · 

        Would be nice to even have a way to disable the scheduler without removing it from Heroku entirely, like for the maintenance mode case above.

      Feedback and Knowledge Base