Runtime: Is there any roadmap for improving GC?
Are there any new GC algorithms in developing?
Would reference counting collector be an alternative memory management mechanism?
ygc369
All 8 comments
Linking threads: https://github.com/dotnet/csharplang/issues/547
swgillespie
on 13 May 2017
What advantages do you think are to be had by switching to a reference counting collector instead of improving the GC we already have? Tracing collectors and reference counting collectors are duals of one another, and each has their own tradeoffs.
cc @Maoni0
swgillespie
on 15 May 2017
@swgillespie
Except RC and Local GC, what can be done to improve the GC we already have? Is anybody doing this?
ygc369
on 16 May 2017
what can be done to improve the GC we already have?
But what exactly do you want to improve about GC?
You keep creating all this GC related issues but you never provide any sort of details - use cases, expectations, numbers, anything - and thus not exactly constructive.
mikedn
on 16 May 2017
@mikedn
I'm sorry. But my mother tongue is not English. It is not easy for me to write a long English article with many details. I can only describe my ideas and I think their advantages are obvious and do not need more explainations.
ygc369
on 16 May 2017
I think their advantages are obvious and do not need more explainations
Nope, there is nothing obvious about the advantages of reference counting.
mikedn
on 16 May 2017
There have been thousands of research papers written about garbage collection, many of them on reference counting. We are aware of all the key ideas that have been published to date. There are folks in Microsoft Research working in this space too. It is very easy to pick and recommend an (existing) idea. The very hard part is how to incorporate it to the system to make it work better for significant fraction of important scenarios.
It is well established that simple reference counting does not work well because of the high cost of the reference count maintenance and inability to collect cycles. There are modifications that try to address it, but nothing obviously better accross the board.
http://gchandbook.org/ is a great summary of different garbage collection ideas with discussion of its process and cons. I would recommend that you to read this book, and try to implement and measure one or two ideas from this book to get a feel for how memory management works in practice before submitting more suggestions here. If you are not able to get access to the book where you live, send me email to my Microsoft address and we will figure out how to get you one.
jkotas
on 16 May 2017
Duplicate of dotnet/csharplang#547 and dotnet/runtime#4029
jkotas
on 16 May 2017
Related issues
aggieben
路
3Comments
noahfalk
路
3Comments
chunseoklee
路
3Comments
iCodeWebApps
路
3Comments
bencz
路
3Comments
Most helpful comment
There have been thousands of research papers written about garbage collection, many of them on reference counting. We are aware of all the key ideas that have been published to date. There are folks in Microsoft Research working in this space too. It is very easy to pick and recommend an (existing) idea. The very hard part is how to incorporate it to the system to make it work better for significant fraction of important scenarios.
It is well established that simple reference counting does not work well because of the high cost of the reference count maintenance and inability to collect cycles. There are modifications that try to address it, but nothing obviously better accross the board.
http://gchandbook.org/ is a great summary of different garbage collection ideas with discussion of its process and cons. I would recommend that you to read this book, and try to implement and measure one or two ideas from this book to get a feel for how memory management works in practice before submitting more suggestions here. If you are not able to get access to the book where you live, send me email to my Microsoft address and we will figure out how to get you one.