Allocations profiler

[Matt Warren]

>* I am not sure how they are able to pull off low-overhead profiling like
*>* that.*

If the question is talking about the same post
(http://blog.matttproud.com/2014/09/go-testing-patterns-benchmark-setup-and.html),
it seems like the memory usage is something provided by the go runtime
itself.

See the -benchmem flag here
https://golang.org/cmd/go/#hdr-Description_of_testing_flags.

So I don't think it comes from a 3rd party profiler, but instead the
runtime itself. So I guess there's still some overhead, but it's
minimal as the go GC must have knowledge of allocations.

Cheers

Matt