--089e011837d4f2b78904db6b9f05 Content-Type: text/plain; charset=UTF-8 On Sat, Apr 27, 2013 at 8:19 PM, ko1 (Koichi Sasada) <redmine / ruby-lang.org>wrote: > We Heroku Matz team developed a new generational mark&sweep garbage > collection algorithm RGenGC for CRuby/MRI. > (correctly speaking, it is generational marking algorithm) > > What goods are: > > * Reduce marking time (yay!) > * My algorithm doesn't introduce any incompatibility into normal C-exts. > * Easy to development > > Please read more details in attached PDF file. > Code is: https://github.com/ko1/ruby/tree/rgengc > > How about to introduce this new GC algorithm/implementation into Ruby > 2.1.0? > > Thanks, > Koichi Another thing: What about passing the old value to OBJ_WB too? OBJ_WB(from, to, old)? In this implementation it would just be a no-op. There are some nice garbage collectors that you can implement if your write-barriers have old values too (e.g "An On-the-Fly Mark and Sweep Garbage Collector Based on Sliding Views"). --089e011837d4f2b78904db6b9f05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir="ltr">On Sat, Apr 27, 2013 at 8:19 PM, ko1 (Koichi Sasada) <spanir="ltr"><<a href="mailto:redmine / ruby-lang.org" target="_blank">redmine / ruby-lang.org</a>></span> wrote:<div class="gmail_extra"><divlass="gmail_quote"> <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> We Heroku Matz team developed a new generational mark&sweep garbage<br> collection algorithm RGenGC for CRuby/MRI.<br> (correctly speaking, it is generational marking algorithm)<br> <br> What goods are:<br> <br> * Reduce marking time (yay!)<br> * My algorithm doesn't introduce any incompatibility into normal-exts.<br> * Easy to development<br> <br> Please read more details in attached PDF file.<br> Code is: <a href="https://github.com/ko1/ruby/tree/rgengc" target="_blank">https://github.com/ko1/ruby/tree/rgengc</a><br> <br> How about to introduce this new GC algorithm/implementation into Ruby 2.1.0?<br> <br> Thanks,<br> Koichi</blockquote><div><br></div><div style>Another thing: What about passing the old value to OBJ_WB too? OBJ_WB(from, to, old)? In this implementation it would just be a no-op. There are some nice garbage collectors that you can implement if your write-barriers have old values too (e.g "An On-the-Fly Mark and Sweep Garbage Collector Based on Sliding Views").</div> </div><br></div></div> --089e011837d4f2b78904db6b9f05--