good first issuehelp wantedperformance
Metriche repository
- Star
- (18.974 stelle)
- Metriche merge PR
- (Merge medio 4g 11h) (85 PR mergiate in 30 g)
Descrizione
This blog post provides a good background / introduction: https://threedots.tech/post/go-test-parallelism/
When I ran the following command
GOMAXPROCS=1 go test -parallel 128 -p 16 -json ./... | go run github.com/roblaszczak/vgt@latest
I got the following output:
It shows some tests running for a very long time (the darker blue colors), but even of some of them were sped up there are others (like in the first group in top left corner) that are still relatively long.
We also almost never use t.Parallel() in our test (right now I only found one instance), even though many of our tests are starting servers and making network calls, so could benefit from parallelism. But adding t.Parallel() should be done with care - some tests are starting servers on the same port (instead of ephemeral port) and must be refactored before adding parallelism.