|author||Russ Cox <firstname.lastname@example.org>||Fri Jun 15 10:40:48 2018 -0400|
|committer||Russ Cox <email@example.com>||Fri Jun 15 20:32:29 2018 +0000|
cmd/go: parallelize module load operations Loading information about modules not yet cached on the local system is dominated by network I/O time. Load the information in parallel to overlap this I/O. As a test case, I am using a real (not synthetic) but unpublished repo with 90 transitive dependencies. In that repo, I've measured the time it takes for rm -rf $GOPATH/src/v && vgo mod -vendor Before this CL, that operation averages about 220 seconds. Adding caching of already-looked-up information in modfetch/repo.go drops the average time to about 170 seconds. Changing the MVS requirement scans to run in parallel drops the average time to about 65 seconds. This CL includes Bryan's comments for mvs.Reqs from CL 116235, extended to document the new parallel access requirements. This CL also adds the build -x flag to 'vgo mod' so that it's possible to see all the git commands being executed. Fixes golang/go#24316. Change-Id: Ia8228e850c6c60d8fa80d2fb3b6773c70e86137b Reviewed-on: https://go-review.googlesource.com/119055 Run-TryBot: Russ Cox <firstname.lastname@example.org> Reviewed-by: Bryan C. Mills <email@example.com> TryBot-Result: Gobot Gobot <firstname.lastname@example.org>
This repository holds a prototype of what the go command might look like with integrated support for package versioning.
See research.swtch.com/vgo for documents about the design.
go get -u golang.org/x/vgo.
You can also manually git clone the repository to
This is still a very early prototype. You are likely to run into bugs. Please file bugs in the main Go issue tracker, golang.org/issue, and put the prefix
x/vgo: in the issue title.