We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack thread which initiated this is here.
At the moment the Tooling Scheduler does not scale down users tooling during the week.
It's currently set to kick-in and schedule tooling down after 16 hours. (link)
There is an opportunity to reduce this number and spin down user compute during the week. This will in turn save money.
No response
If we... [do a thing] Then... [this will happen]
Tooling Scheduler - Proposed change comms
Example - [ ] Documentation has been written / updated
The text was updated successfully, but these errors were encountered:
Change comms written and ready to be sent to users via analytical-platform-support slack channel
Sorry, something went wrong.
simon-pope
No branches or pull requests
User Story
Slack thread which initiated this is here.
At the moment the Tooling Scheduler does not scale down users tooling during the week.
It's currently set to kick-in and schedule tooling down after 16 hours. (link)
There is an opportunity to reduce this number and spin down user compute during the week. This will in turn save money.
Definition of Done
Value / Purpose
No response
Useful Contacts
No response
User Types
No response
Hypothesis
If we... [do a thing]
Then... [this will happen]
Proposal
No response
Additional Information
Tooling Scheduler - Proposed change comms
Definition of Done
Example - [ ] Documentation has been written / updated
The text was updated successfully, but these errors were encountered: