-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
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
Review DCR Scaling Policy #9311
Milestone
Comments
Implemented a step scaling policy in #10127 |
Moving to backlog after merging #10127 since there are further opportunities to improve the scaling logic and these can be addressed in future health weeks |
Re-opening here: |
mxdvl
changed the title
Review DCR Scaling Policy
Review DCR Scaling Policy & Provisioning
Jul 8, 2024
mxdvl
changed the title
Review DCR Scaling Policy & Provisioning
Review DCR Scaling Policy
Jul 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ticket created from #8345 (comment)
This ticket is to:
DCR Scaling Policy
DCR is currently using Simple Scaling Policy1. AWS have essentially deprecated this style of scaling and are promoting their alternative solutions as a best practice:
Do we want to consider adopting one of the other alternatives?
Some examples in other Guardian repos:
TargetTrackingScaling
in ARStepScaling
in OphanDCR Scaling Policy Metric
We're currently scaling based on latency:
dotcom-rendering/dotcom-rendering/cdk/lib/dotcom-rendering.ts
Lines 296 to 301 in 8392773
and scaling up by doubling our capacity every 10 minutes:
dotcom-rendering/dotcom-rendering/cdk/lib/dotcom-rendering.ts
Lines 272 to 277 in 8392773
whilst scaling down by removing an instance once every 2 minutes:
dotcom-rendering/dotcom-rendering/cdk/lib/dotcom-rendering.ts
Lines 278 to 283 in 8392773
Do we want to consider other scaling strategies? Apps-rendering, for example, via
guardian/cdk
, scales based on a target CPU utilisation:dotcom-rendering/apps-rendering/cdk/lib/mobile-apps-rendering.ts
Lines 104 to 106 in e234547
Tasks
Footnotes
Simple scaling is the default, so if
PolicyType
is unspecified,SimpleScaling
is used. ↩The text was updated successfully, but these errors were encountered: