Ravi
Ravi
## What does this change? Follow up to https://github.com/guardian/dotcom-rendering/issues/9311 Adds a CPU utilization based [target](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-target-tracking.html) scaling policy ## Why? We could use this policy [in addition](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scale-based-on-demand.html#multiple-scaling-policy-resolution) to the current latency...
We've had reports of high CPU usage preventing user interaction with the page. 1)  2) https://github.com/guardian/dotcom-rendering/issues/11927#issuecomment-2238717103 Interesting to note `window.navigator` is referenced in both reports
We have observed spikes in requests to the Frontend stack without seeing corresponding increased requests to router. This leads us to believe there is retry behaviour in router (an nginx...
Tests scenarios have not been updated since DCR article migration days and hence many of the tests are not relevant anymore. For concrete metrics like JS size, page weight, etc...
When running `make compile` in Frontend lots of SASS deprecation warnings are generated. Could we a) configure the SASS compiler to _not_ emit deprecation warnings? b) fix the deprecation warnings?...
As reported by @sndrs When running `make compile` in Frontend the following error/warning is reported: ``` Body from GETting 'https://vendorlist.consensu.org/vendorlist.json' is not valid JSON Falling back to [redacted]/code/frontend/static/vendor/data/cmp_fallback_vendorlist.json ``` This...