Re: [go-nuts] Modern Garbage Collection Article

2016-12-20 Thread Jesper Louis Andersen
The key observation of a GC: It must match modern hardware, and it must match the programming language for which you write it for. Historically, Java allocated all objects on the heap. This adds GC pressure and in order to remove such GC pressure, you are soon reaching for a generational GC model.

Re: [go-nuts] Modern Garbage Collection Article

2016-12-20 Thread 'Alan Donovan' via golang-nuts
On 20 December 2016 at 11:17, wrote: > > compare 1 pointer in Go's string to 3 in java.lang.String > Sorry, "2 in java.lang.String". -- 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 i

Re: [go-nuts] Modern Garbage Collection Article

2016-12-20 Thread adonovan via golang-nuts
On Tuesday, 20 December 2016 00:31:52 UTC-5, Ian Lance Taylor wrote: > > [Go] is designed to let you control when and > how memory is allocated, giving you control over when memory is > allocated. The effect is that in Go you can adjust your program to > reduce GC overhead, rather than tuning t

Re: [go-nuts] Modern Garbage Collection Article

2016-12-19 Thread andrey mirtchovski
My apologies to the original author, but the "state of the art" of modern garbage collectors is not acceptable if it means this: "To run dex in process, the Gradle daemon needs a larger heap. It currently has 1024 MB. For faster builds, increase the maximum heap size for the Gradle dae

Re: [go-nuts] Modern Garbage Collection Article

2016-12-19 Thread Konstantin Khomoutov
On Mon, 19 Dec 2016 20:56:39 -0800 (PST) Tyler Compton wrote: > https://medium.com/@octskyward/modern-garbage-collection-911ef4f8bd8e#.c48w4ifa7 > > Thoughts? How accurate is this article? If it is, why, historically, > is the work being done on the GC so concentrated on pause times? > > For mo

Re: [go-nuts] Modern Garbage Collection Article

2016-12-19 Thread Tyler Compton
Thank you for your input! > Throwing more cores at the problem is a sensible approach on modern hardware. Since the cores are no longer getting faster, making your code run faster on a single core is not the optimal design for the hardware of the near future. I had not considered increasing c

Re: [go-nuts] Modern Garbage Collection Article

2016-12-19 Thread Ian Lance Taylor
On Mon, Dec 19, 2016 at 8:56 PM, Tyler Compton wrote: > https://medium.com/@octskyward/modern-garbage-collection-911ef4f8bd8e#.c48w4ifa7 > > Thoughts? How accurate is this article? If it is, why, historically, is the > work being done on the GC so concentrated on pause times? If you click on the

[go-nuts] Modern Garbage Collection Article

2016-12-19 Thread Tyler Compton
https://medium.com/@octskyward/modern-garbage-collection-911ef4f8bd8e#.c48w4ifa7 Thoughts? How accurate is this article? If it is, why, historically, is the work being done on the GC so concentrated on pause times? For more discussion: https://www.reddit.com/r/golang/comments/5j7phw/modern_gar