> amazing, Thank you for that detailed breakdown!
when one does something for a long time and understands the system
well they develop an intuition for where the problems may lie. this is
true in every profession...
--
You received this message because you are subscribed to the Google Groups
"g
amazing, Thank you for that detailed breakdown!
On Friday, April 21, 2017 at 10:08:02 AM UTC-7, Jesper Louis Andersen wrote:
>
> On Fri, Apr 21, 2017 at 5:58 PM st ov >
> wrote:
>
>> @Jesper, curious how you determined that?
>> Is it in the spec? or the source?
>> Or is this a common GC patter
I cheated, I used godep to put everything into a /vendor folder and then
did a quick search.
Turns out the only calls are in the stackimpact.com code!
https://github.com/stackimpact/stackimpact-go/search?utf8=✓&q=runtime.GC%28%29&type=
I've reached out to them but any insight there would be
Anyone think of an easy way to search for it's usage? 😆
On Friday, April 21, 2017 at 6:11:25 PM UTC+1, Lee Armstrong wrote:
>
> Thanks again all,
>
> Interestingly I noticed the same and my code does not call runtime.GC() so
> that is a good spot.
>
> I wonder if something I have imported is doin
Thanks again all,
Interestingly I noticed the same and my code does not call runtime.GC() so
that is a good spot.
I wonder if something I have imported is doing so, I will audit all of the
imports and take a look!
On Friday, April 21, 2017 at 6:08:02 PM UTC+1, Jesper Louis Andersen wrote:
>
>
On Fri, Apr 21, 2017 at 5:58 PM st ov wrote:
> @Jesper, curious how you determined that?
> Is it in the spec? or the source?
> Or is this a common GC pattern that you presume is being used?
>
>
There are a couple of design documents by Clements and Hudson which are
worth reading. They are well wr
@Jesper, curious how you determined that?
Is it in the spec? or the source?
Or is this a common GC pattern that you presume is being used?
On Thursday, April 20, 2017 at 7:01:03 AM UTC-7, Jesper Louis Andersen
wrote:
>
> A somewhat common culprit seems to be the following case:
>
> 1. In order
A somewhat common culprit seems to be the following case:
1. In order for the GC to switch from marking to sweeping, it needs all
cores to agree. This requires a "barrier" in the system and thus we have to
wait on all CPUs.
2. The barrier check happens on a function call.
3. A CPU core is currentl
