cmd/compile: 1.12 compiler needs double the memory than 1.11 #32089
Labels
FrozenDueToAge
ToolSpeed
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
What version of Go are you using (
go version
)?1.12.4
vs1.11.2
Details
We (https://github.com/google/gapid) generate go code based off our own domain specific language. We generate 2 go packages each with about 500k LOC. I have observed that the memory needed by the go compiler for these packages has doubled in 1.12 compared to 1.11. In 1.11, the compile executable used between 3.5G and 4G of RAM for each package, while the 1.12 version needs ~8G (resident memory, virtual memory is even more). I have observed this on both X86_64 Linux and MacOS. This causes our build bots to run out of memory and the compile fails with the below stack trace.
I don't know if you can fix this, but I felt that doubling the memory usage is a significant enough performance regression you might want to know about.
The text was updated successfully, but these errors were encountered: