Re:Ruby Garbage Collection: Still Not Ready for Production
by wbl on Friday March 28, 2014 @02:36PM
(#7489107)
Performance suffers. Every write requires an adjustment to an object's reference count, and if you have objects that can be cross-thread an atomic test-set at that. The underlying allocator has to deal with fragmentation, because there is no copying. Furthermore, every object grows a count field.
[ Parent
| on HN ]
There are no comments on this comment yet.