This message was deleted.

sparse-intern-71089

09/29/2020, 4:26 PM

This message was deleted.

lemon-agent-27707

09/29/2020, 4:44 PM

Are you by any chance running pulumi inside of a VM? Due to a lack of generics in go, there are a huge number of types that get linked in and this is known to take up quite a bit of memory.

lemon-agent-27707

09/29/2020, 4:46 PM

Are you able to build the binary before running

pulumi up

or does that fail as well?

big-account-56668

09/29/2020, 5:19 PM

I am not running inside a VM, yet. This is on my laptop which has 16gb of total memory. Do you think that is not enough?

big-account-56668

09/29/2020, 5:21 PM

I tried building the binary on it's own which caused the same long-running compilation. Let me see if it finishes if I leave it for a while longer.

big-account-56668

09/29/2020, 5:25 PM

No, building the binary also results in the same error, but I can see now that it's indeed being killed off by the OOM-killer:

Copy code

[ 6559.889281] Out of memory: Killed process 15267 (compile) total-vm:10209944kB, anon-rss:9480132kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:18764kB oom_score_adj:0

Any suggestions on how to proceed here?

lemon-agent-27707

09/29/2020, 5:32 PM

Can you try setting GOGC? Perhaps something like

GOGC=50

GOGC=25

https://dave.cheney.net/tag/gogc

big-account-56668

09/29/2020, 5:49 PM

Setting a lower

GOGC

value seems to help as the compilation now succeeds so I can get around my particular issue this way for now, thanks.

big-account-56668

09/29/2020, 5:51 PM

As I suspected this is only needed when recompiling, in this case, the

compute

package.

2 Views

Open in Slack

Previous Next

Pulumi Community

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.