go 1.13.1 (linux x64): Build and Test is slower.

[Stuart Davies]

Hi.

I use a low spec laptop that I take with me so I can work/play in the coffee shop!

Since upgrading go to 1.13 I have noticed a significant slow down (2 to 3 times) in build and build for test especially when debugging.

It is still fast compared to other languages I use but I was sooo impressed by the build times previously that I am very concious of the slower performance.

I am using VSCode ar an IDE and have made sure I am up to date with all the tools.

I am using modules as well so perhaps this is the issue but all my code is local and I have a 'replace' in the go.mod file.

My project is outside GOPATH directory but GOPATH is still defined.

Is ther esomthing I can do to restore the performance of is this 'Progress' and I will just have to et usd to it.

Please keep up the good work. Go is the first language for years that I felt I could invest time in. As a Java dev for many years and the frustrations that brings, Go is a refreshing change.

Please keep the language simple and dont get dragged in to the me-too feature debate. Go is a really great language already..

[Miguel Angel Rivera Notararigo]

Hello :) I think you need to give some samples of what you are doing because without that the people that know about how to solve that problem cant help you. Remember, there are a lot of factors that may increase the building time, could you share at least something like time go build with both versions (1.13 and 1.12)?

[Stuart Davies]

Ok I will just get on with it. I am not is a position to compare performance when there are so many variables.

I thought others might have had the same issue and there might be a simple explanation.

We can close this discussion.

[ja...@necival.com]

Hey Stuart, I believe that it is most likely Go modules, I had tested adding go modules to my project and immediately my build times went from almost instant to noticeable. I reverted, and the build times went back to normal. I think this is because Go modules checks for module updates on each build. I have a private git in my import, and it prompted me for the git username/password each time I'd build too, which was the deciding factor for me. I could deal with a 5-10s builds, but having to enter my u/p each time was too much. Hope this helps