3 Commits

Author	SHA1	Message	Date
Shenghou Ma	13075ed416	test/bench/go1: use raw string instead of string addition ... to reduce compile time memory/stack usage. Update #4970 $ go test -c ../test/bench/go1 before: 0.36user 0.07system 0:00.44elapsed 100%CPU (0avgtext+0avgdata 540720maxresident)k 0inputs+19840outputs (0major+56451minor)pagefaults 0swaps after: 0.33user 0.05system 0:00.39elapsed 100%CPU (0avgtext+0avgdata 289936maxresident)k 0inputs+19864outputs (0major+29615minor)pagefaults 0swaps And stack usage is reduced to below 1MiB. R=golang-dev, r, dave CC=golang-dev https://golang.org/cl/7436050	2013-03-05 04:23:37 +08:00
Shenghou Ma	6b4ae1d28e	test/bench/go1: fix gzip test ... We can't depend on init() order, and certainly we don't want to register all future benchmarks that use jsonbytes or jsondata to init() in json_test.go, so we use a more general solution: make generation of jsonbytes and jsondata their own function so that the compiler will take care of the order. R=golang-dev, dave, rsc CC=golang-dev https://golang.org/cl/6282046	2012-06-05 00:14:39 +08:00
Russ Cox	6e8875551a	test/bench/go1: first draft of Go 1 benchmark suite ... I have included a few important microbenchmarks, but the overall intent is to have mostly end-to-end benchmarks timing real world operations. The jsondata.go file is a summary of agl's activity in various open source repositories. It gets used as test data for many of the benchmarks. Everything links into one binary (even the test data) so that it is easy to run the benchmarks on many computers: there is just one file to copy around. R=golang-dev, r, bradfitz, adg, r CC=golang-dev https://golang.org/cl/5484071	2011-12-15 12:32:59 -05:00