The cost of write barriers
Paulo Pinto via Digitalmars-d
digitalmars-d at puremagic.com
Sun Nov 2 05:13:16 PST 2014
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
More information about the Digitalmars-d
mailing list