post on using go 1.5 and GC latency

[rsw0x via Digitalmars-d-learn]

On Saturday, 22 August 2015 at 09:16:32 UTC, Russel Winder wrote:
> On Sat, 2015-08-22 at 07:30 +0000, rsw0x via 
> Digitalmars-d-learn wrote:
>> [...]
>
> Not entirely true. Go is a general purpose language, it is a 
> successor to C as envisioned by Rob Pike, Russ Cox, and others 
> (I am not sure how much input Brian Kernighan has had). 
> However, because of current traction in Web servers and general 
> networking, it is clear that that is where the bulk of the 
> libraries are. Canonical also use it for Qt UI applications. I 
> am not sure of Google real intent for Go on Android, but there 
> is one.
>
>> [...]
>
> They also saw a 100% increase in performance when it was 
> rewritten, and a 20% fall with this latest rewrite. I 
> anticipate great improvement for the 1.6 rewrite.  I am 
> surprised they are retaining having only a single garbage 
> collector: different usages generally require different garbage 
> collection strategies. Having said that Java is moving from 
> having four collectors, to having one, it is going to be 
> interesting to see if G1 meets the needs of all JVM usages.
>
>> [...]
>
> Until some organization properly funds a suite of garbage 
> collectors for different performance targets, you have what 
> there is.

The performance decrease has been there since 1.4 and there is no 
way to remove it - write barriers are the cost you pay for 
concurrent collection. Go was already much slower than other 
compiled languages, now it probably struggles to keep up with 
mono.