Changes between Version 5 and Version 6 of Commentary/Rts/Storage/GC/RememberedSets
- Jun 9, 2013 1:30:21 PM (2 years ago)
v5 v6 16 16 but it is faster at runtime if a lot of mutation is taking place, and it takes less space than a remembered set. In GHC 17 17 we typically do not have much mutation to worry about, so card marking would be a poor compromise in our case. 18 19 GHC currently has a performance bug related to its representation of remembered sets: 20 21 [[TicketQuery(id=650|)]] 22 23 the problem here is that our policy of tracking only the pointer to the array in the remembered set has lead to severe performance problems; either of the other two representations would be better. 24 18 25 19 The remembered set may contain duplicates, or it may contain pointers to objects that don't really point to young generations.