Ian Lance Taylor's Response to “Go Is Google's Language”

Re:Ian Lance Taylor's Response to “Go Is Google's Language” by grumpydba on Wednesday May 29, 2019 @03:14PM (#20044176)

Object pools are really easy. Unsafe is only for extreme cases. Some cache libraries use it. You don't have to code it yourself. Yes this is better than relying on the end user/admin to tune things. It is more predictable.

[ Parent | on HN ]

Re:Ian Lance Taylor's Response to “Go Is Google's Language” by apta on Wednesday May 29, 2019 @11:45PM (#20048186)

Managing allocations is way more than just object pooling. The following code in golang allocates "n" on the heap:

    func main() {
        n := 1
        fmt.Println(n)
    }

Object pooling won't help here.

The new GCs on the JVM have very few parameters to tune, I think Shenandoah or ZGC have only two parameters to set up, can't get much simpler.

[ Parent | on HN ]

Re:Ian Lance Taylor's Response to “Go Is Google's Language” by grumpydba on Friday May 31, 2019 @06:30AM (#20059668)

You can pool n if it's on your hot path, can't you?

Escape analysis was just rewritten, and the objective is to handle this case more gracefully.

[ Parent | on HN ]