No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Shouldn't be - in general performance should be dominated by the operations needed to Create/Read/Update/Delete resources in your cloud.

What specifically are you seeing be slow?

Hi <@UB3BGTV63> I have around 150 Kubernetes resources created with Pulumi. It takes a while to run the update command

You mean it take time to deploy all 150 resoruces initially?  Or it also takes a long time to do an update when nothing needs to change?

Deploying 150 new resources (and waiting for them to be ready) may certainly take awhile depending on the resources and your cluster.

No, it takes quite a while also when just updating small things after the initial create

Are you on recent versions of `pulumi` CLI and `@pulumi/kuberentes` packages?

If so - could you follow instrusctions here and DM me the results so we can look into it?

<https://www.pulumi.com/docs/troubleshooting/#performance>

For example now I am testing some changes to a config map. It takes maybe 20s before it asks me if I want to update, and then around 1m25s to change the config map

Yep I think I have the latest updates. I installed it a couple of days ago

If I share a trace, does it contain any sensitive info?

Screen Shot 2020-03-26 at 1.25.09 PM.png

Screen Shot 2020-03-26 at 1.25.05 PM.png

It could potentially.  You can also view locally and share screenshots of key pieces.

If you do you will want to "Show Children" on the root `pulumi` node and Sort by Start Time.

Ok I'll finish polishing my current code and try. Thanks!