go build helloworld.go takes 12sec cpu time on my laptop and gets compile timeout on our server.
subsequent go builds run much faster though (less than 1sec, even when compiling a completely different program). i guess it's compiling half of the stdlib on first invocation and stuffing it into ~/.cache/go-build? then we need to figure out a place where to put the cache so that go build inside the isolate sandbox can read it... (but not write to it, that would be insecure.)
go build helloworld.gotakes 12sec cpu time on my laptop and gets compile timeout on our server.subsequent
go builds run much faster though (less than 1sec, even when compiling a completely different program). i guess it's compiling half of the stdlib on first invocation and stuffing it into ~/.cache/go-build? then we need to figure out a place where to put the cache so thatgo buildinside the isolate sandbox can read it... (but not write to it, that would be insecure.)