Open j08lue opened 2 days ago
aside: @smohiudd @j08lue @stephenkilbourn I wonder if we ran the playwright tests on a schedule would help keep the services for the dashboard warm? I thought the status page would be enough to keep a minimal number of lambdas awake but we should also review the backend logs to see how often cold starts are happening.
aside: @smohiudd @j08lue @stephenkilbourn I wonder if we ran the playwright tests on a schedule would help keep the services for the dashboard warm?
Playwright should hit every api endpoint that the app uses on a load. it may be simpler and less overhead to just keep the lambda warm with a schedule event bridge rule, though. https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-create-rule-schedule.html
As a casual reader of an article, I expect key figures and widgets to load instantaneously, so I can quickly browse an article before diving in deeper.
Currently, maps embedded in stories and other articles can take a long time to load (20s or so).
Once cached (in the browser), scrolling past the map works nicely.
Is there a way to improve this? E.g. by triggering the embedded maps to start fetching the tiles as the story/page loads, not only when I load the map?
Same goes for scrollytelling.
Acceptance criteria