This message was deleted Pulumi Community #general

Join Slack

This message was deleted.

# general

sparse-intern-71089

10/23/2019, 2:12 PM

This message was deleted.

white-balloon-205

10/23/2019, 3:36 PM

We’ve made some very significant performance improvements in the recent versions of

@pulumi/kubernetes

and the

Pulumi

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-96441

10/24/2019, 2:28 PM

CLI version should be the latest: in CI/CD we install the newest version on every invocation Furthermore, we're only using @pulumi/pulumi and @pulumi/aws. As I saw in the issues you optimized some things a while ago? I'll check against the newest versions and probably grab a trace. Thanks

future-morning-96441

10/25/2019, 8:58 AM

@white-balloon-205 I sent you a trace in DM. Pulumi-CLI: 1.4.0 resource plugin: aws-0.18.27 in package-lock.json: @pulumi/pulumi: 0.17.28 @pulumi/aws: 0.18.27 Wait, just realized, the required npm-packages are pretty outdated. Will update pulumi npm packages and report back.

future-morning-96441

10/25/2019, 11:34 AM

after updating all packages to current version,

pulumi up

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

2 Views

Open in Slack

Previous Next