You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Daniel Martí 091f8239c0 rework the build benchmarks ... First, stop writing binaries into the current directory, which pollutes the git clone. Second, split the benchmark into two. The old benchmark always used the build cache after the first iteration, meaning that we weren't really measuring the cost of cold fresh builds. The new benchmarks show a build with an always-warm cache, and one without any cache. Note that NoCache with the main package importing "fmt" took about 4s wall time, which makes benchmarking too slow. For that reason, the new bench-nocache program has no std dependencies other than runtime, which already pulls in half a dozen dependencies we recompile at every iteration. This reduces the wall time to 2s, which is bearable. On the other hand, Cache is already fast, so we add a second and slightly heavier dependency, net/http. The build still takes under 300ms of wall time. This also helps the Cache benchmark imitate larger rebuilds with a warm cache. Longer term, both benchmarks will be useful, because we want both scenarios to be as efficient as possible. name time/op Build/Cache-8 161ms ± 1% Build/NoCache-8 1.21s ± 1% name bin-B Build/Cache-8 6.35M ± 0% Build/NoCache-8 6.35M ± 0% name sys-time/op Build/Cache-8 218ms ± 7% Build/NoCache-8 522ms ± 4% name user-time/op Build/Cache-8 825ms ± 1% Build/NoCache-8 8.17s ± 1%		3 years ago
..
main.go	rework the build benchmarks	3 years ago