The cost of write barriers

[Paulo Pinto via Digitalmars-d]

On Sunday, 2 November 2014 at 13:13:17 UTC, Paulo Pinto wrote:
> On Sunday, 2 November 2014 at 08:48:46 UTC, Jonathan Barnard 
> wrote:
>> The upcoming version 1.4 of Go uses write barriers in 
>> preparation for the future implementation of a concurrent and 
>> generational GC. On the mailing list thread discussing the 
>> beta 
>> (https://groups.google.com/forum/#!topic/golang-nuts/7VAcfULjiB8), 
>> a few people note speed reductions of 30-50% in their 
>> benchmarks. I think this vindicates to a degree D's decision 
>> to avoid garbage collection strategies that require write 
>> barriers.
>
> Please also mention that those reductions are happening because 
> the new code hasn't been optimized yet and Go 1.5 will get a 
> concurrent generational GC.
>
> --
> Paulo

Ooops, pressed send too soon. :(

I just wanted to mention the part that Go team is aware that the 
code still hasn't been fully optimized.

Sorry for the second part of the sentence. You did mentioned it.

--
Paulo