This message was deleted.
# golang
s
This message was deleted.
l
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.
Are you able to build the binary before running
pulumi up
or does that fail as well?
b
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?
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.
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?
l
Can you try setting GOGC? Perhaps something like
GOGC=50
or
GOGC=25
https://dave.cheney.net/tag/gogc
b
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.
As I suspected this is only needed when recompiling, in this case, the
compute
package.