Re: [go-nuts] runtime.GC - documentation

2016-11-30 Thread 'Austin Clements' via golang-nuts
On Tue, Nov 29, 2016 at 6:57 PM, Rick Hudson wrote: > That is correct. ... but not guaranteed. :) -- 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

Re: [go-nuts] runtime.GC - documentation

2016-11-29 Thread Rick Hudson
That is correct. On Tuesday, November 29, 2016, Josh Hoak wrote: > To clarify, the GC method has different behavior than how the background > garbage collector works. GC calls gcStart with blocking mode, whereas the > normal background garbage collector is called from proc.go

Re: [go-nuts] runtime.GC - documentation

2016-11-29 Thread Josh Hoak
To clarify, the GC method has different behavior than how the background garbage collector works. GC calls gcStart with blocking mode, whereas the normal background garbage collector is called from proc.go and malloc.go

Re: [go-nuts] runtime.GC - documentation

2016-11-29 Thread Rick Hudson
The documentation is correct. The current runtime.GC() implementation invokes a Stop The World (STW) GC that completes before runtime.GC() returns. It is useful when doing benchmarking to avoid some of the non-determinism caused by the GC. On Tue, Nov 29, 2016 at 1:15 PM, Ian Lance Taylor

Re: [go-nuts] runtime.GC - documentation

2016-11-29 Thread Ian Lance Taylor
[ +rlh, austin ] On Tue, Nov 29, 2016 at 7:29 AM, Carlos wrote: > Hi, > > > In https://golang.org/pkg/runtime/#GC it says: > >> It may also block the entire program. > > > Is this still correct? I understand that GC still pauses, but being under > 100us mark I wonder