Performance degradation with custom endpoints #2880
Labels
impact/performance
Something is slower than expected
impact/regression
Something that used to work, but is now broken
kind/bug
Some behavior is incorrect or out of spec
p1
A bug severe enough to be the next item assigned to an engineer
resolution/fixed
This issue was fixed
Milestone
What happened?
The 6.x versions of the package introduced some serious performance degradation to anyone who works with multiple custom endpoints in their stack config.
See a run comparison below in the example for a simple
pulumi preview
command between the current latest (v6.5.0) vs v5.41. As I've noticed every single custom endpoint increases the run time by 1.5-4s which in case of the usage ofpulumi-local
, that generates the endpoints for all AWS services (~250) into the config file for Localstack, results in a significant run time up to 500-800s without even start to work on the actual deploy.To exclude
Localstack
as the source of fault from the batch, no request arrived during these runs to the container and I couldn't find any indication in Pulumi's log that it would send any (the option I used was-v 3
).Example
Config:
index.ts:
package.json for 6.5.0:
Run output:
package.json for 5.41.0:
Run output:
Output of
pulumi about
For 6.5.0:
For 5.41.0:
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: