future-morning-9644110/23/2019, 2:12 PM
The Stack's number of resources grew over time and so did the time needed for a deployment (also for updates in a single lambda). I'm thinking of many different approaches of how to speed up thinks, but it would be great to be able to prioritize tasks based on the expected speedup.
Metrics I would be interested in could include:
- time needed to run diff before update
- time needed to upload a lambda
- time needed for requests to Pulumi backend
- maybe also overall and split into resource-types
We are already thinking about splitting the application into several stacks. But still, I'd like to perform an informed choice of where and how to start optimizing our deployment times.
PS: last deployment took about 36 minutes:
- 36 updated ressources
- 476 unchanged resource
Kind regards, Chris
CLI. If you aren’t already on the latest - I’d suggest trying those to see if things have improved. Based on what you describe - this sounds like one of the issues that was recently addressed.
If not - you can grab a trace and share with us by following: https://github.com/pulumi/pulumi/issues/3257#issuecomment-534629119
future-morning-9644110/24/2019, 2:28 PM
took even longer: 50 minutes for 36 updated and 476 unchanged ressources.
Sadly I couldn't get a trace fir this update, because CI/CD ran out of memory