-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
initial pulumi preview (Go) on datadog SDK consumes more than 10GB of memory on V4 and 4GB on V3 #561
Comments
Hey @yishait-tailor. Thanks for reporting this bug. The provider definitely shouldn't use that much memory. Just to clarify, what do you mean by the "first run"?
Can you check how much memory |
Hey @iwahbe! by the looks of it, running Are you saying that when you create a new stack with datadog, the first pulumi up uses 10gb
Are you saying that the initial run of pulumi up in each container takes 10gb?
the workaround is to create the docker image with the go binary file produced by running
Thanks! |
Hey @yishait-tailor. That clarifies the problem nicely. The problem is that the go SDK for pulumi-datadog is simply too big. I'll take a look at reducing the number of types we export. This is related to pulumi/pulumi-terraform-bridge#1468. |
Describe what happened
Running
pulumi preview
on any resource in datadog SDKwith V4 consumes more than 10GB of memory on first run
V3 consumes more than 4GB of memory
using:
github.com/pulumi/pulumi-datadog/sdk/v4/go/datadog
github.com/pulumi/pulumi-datadog/sdk/v3/go/datadog
using the examples only with no changes
tested on several platforms all same behavior
using s3 as backend without pulumi account
Is there any way to avoid this?
Sample program
Log output
Affected Resource(s)
every initial
pulumi preview
runOutput of
pulumi about
Additional context
Im trying to use this SDK in CI on ephemeral containers,
and i don't want to allocate such a high amount of memory just for the first run.
This happens with all Datadog SDK resources
And not on other pulumi SDKs
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: