Go Pacmak OOM Crash and Performance

[MrArnoldPalmer]

We have received reports that jsii-pacmak can run out of memory causing crashes on large packages while doing Go code generation. Additionally we have seen the time it takes to generate go packages is significantly higher than other languages.

This is somewhat expected as the Go code generation is built differently than the other languages since it is the only generator that was built with submodule support in mind. There may be a number of easy optimizations to reduce memory usage and overall runtime via memoization during both first pass AST generation and second pass output.

[ansgarm]

This is resolved by #3362, isn't it?

[MrArnoldPalmer]

correct, should be improved in the next release.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.