Can you share a small runable reproduction which shows the problem ?

On Tuesday, 20 September 2016 23:26:29 UTC+10, Ethan Kennedy wrote:
> Dave,
> Thank you for the tip. That does at least show me some measurements of 
> allocations. I guess I was hoping to do some more fine-grained analysis, if 
> only as an educational exercise.
> So, I tried using the runtime/pprof package to write a heap profile at a 
> specific point in my program and still got some less than informative 
> results. I'm wondering if this means my program is triggering GC at a point 
> where I'm not expecting it, which is preventing capture of a good profile.
> On Monday, September 19, 2016 at 5:18:56 PM UTC-5, Dave Cheney wrote:
>> Try b.ReportAllocs() before your benchmark loop. That's the easiest way 
>> to benchmark the allocations per operation.

You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to