GC Tuning Confessions of a Performance Engineer

Re:GC Tuning Confessions of a Performance Engineer by bd_at_rivenhill on Friday May 29, 2015 @02:16PM (#9626328)

I think we will start to see less use of GCs in mobile going forward, especially now that Apple has deprecated GC in favor of automatic reference counting. The issues caused by the interaction between the memory hierarchy and the fragmentation that is naturally introduced by GC are difficult to measure, but nevertheless an important component of performance.

[ Parent | on HN ]

Re:GC Tuning Confessions of a Performance Engineer by banachtarski on Friday May 29, 2015 @07:26PM (#9628148)

Reference counting is still not the same as manual memory management, and there is a heavy cost to reference counting as well. Reference counting trades throughput for latency relative to a garbage collected runtime.

[ Parent | on HN ]

Re:GC Tuning Confessions of a Performance Engineer by pjmlp on Friday May 29, 2015 @02:24PM (#9626381)

Lets not forget they did that, because they failed to produce a stable working GC for Objective-C.

[ Parent | on HN ]

Re:GC Tuning Confessions of a Performance Engineer by Drdrdrq on Friday May 29, 2015 @03:20PM (#9626705)

Lets not forget Java failed to produce that too, they just dont seem to care. :)

[ Parent | on HN ]

Re:GC Tuning Confessions of a Performance Engineer by pjmlp on Friday May 29, 2015 @03:26PM (#9626748)

I didn't notice that JVM's GC do segfault all the time, with erratic behaviour depending on the libraries being linked.

[ Parent | on HN ]

Re:GC Tuning Confessions of a Performance Engineer by vitalyd on Friday May 29, 2015 @05:10PM (#9627469)

A performant GC for mobile is inherently a much harder problem than for servers.

[ Parent | on HN ]