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

What version of Pulumi is this?

There were some performance issues awhile ago that could cause very large stacks to take time proportional to the number of resources in the stack instead of the number of resources that changed - but those were fixed several months ago.

Thanks for taking this a look.
The version I am using is v2.5.0
```$ pulumi version
v2.5.0```

<@UB3BGTV63> I did log this issue for a similar reason (<https://github.com/pulumi/pulumi/issues/4936>)

We tend to add new things more than they are updated or changed (drift). We were hoping we could speed up the stack computation if we can tell it to just target new resources only which would speed it up. Now that said I have done tests to see if it isn't really a stack probably but the backend but our stacks tend to be large.

<@UB3BGTV63> I did log this issue for a similar reason (<https://github.com/pulumi/pulumi/issues/4936>)

I tend to add new things more than they are updated or changed (drift). I was hoping we could speed up the stack computation if we can tell it to just target new resources only which would speed it up. Now that said I haven't done tests to see if it isn't really a stack probably but the backend but my stacks tend to be large.

Could you grab the diagnostics listed at <https://www.pulumi.com/docs/troubleshooting/#performance|https://www.pulumi.com/docs/troubleshooting/#performance> and share a copy of the output in DM?  That might help us pinpoint why this is taking so long. It is definitely not expected performance. 

I wasn't able to get to this today. I hope to gather the info for you tomorrow.