tree 1c0e59f39407b2715faa35d47fcd09253ebcb9e8
parent d52538816fa9e3e6b72839f4df83fb35164e2e12
author Dmitriy Vyukov <dvyukov@google.com> 1413786235 +0400
committer Dmitriy Vyukov <dvyukov@google.com> 1413786235 +0400
golang-hg 82cb5aac589f2985a93a882e181cfff7f07d28fc

driver: fix latency collection
This change:
http://build.golang.org/perfdetail?commit=28de6f41b1c77c5cb9046056fb29b96b9583a3a5&commit0=90a7c3c86944759bd88007c09f7a311c42f4bef8&builder=linux-amd64-perf&benchmark=http
shows +25% heap size increase on linux/http-8.
I've looked at the logs and the reason is that during benchmarking of the old commit
all runs used 500000 iterations:

2014/10/17 21:32:15 Benchmarking 500000 iterations
gc1058(8): 31+57+758+24 us, 8 -> 16 MB, 143644 (126950432-126806788) objects, 136 goroutines, 1586/0/657 sweeps, 202(6287) handoff, 26(217) steal, 438/13/0 yields

And during benchmarking of the new commit one of the runs used 1000000 iterations:

2014/10/17 21:38:51 Benchmarking 1000000 iterations
gc540(8): 29+33+1082+13 us, 12 -> 24 MB, 194738 (63964975-63770237) objects, 136 goroutines, 2019/0/658 sweeps, 227(5856) handoff, 35(251) steal, 656/107/7 yields

This resulted in twice larger latency array. Which is 4MB.
Multiplied by GOGC gives exactly the additional 8MB reported.

Simply create maximum latency array always.

LGTM=adg
R=adg, bradfitz
CC=golang-codereviews
https://golang.org/cl/156340043