[prev in list] [next in list] [prev in thread] [next in thread]
List: ruby-core
Subject: [ruby-core:54718] [ruby-trunk - Feature #8339] Introducing Geneartional Garbage Collection for CRuby
From: "sam.saffron (Sam Saffron)" <sam.saffron () gmail ! com>
Date: 2013-04-30 11:00:46
Message-ID: redmine.journal-39063.20130430200045 () ruby-lang ! org
[Download RAW message or body]
Issue #8339 has been updated by sam.saffron (Sam Saffron).
Confirmed the recent push resolves it, will try to gather some benchmarks against Discourse tomorrow.
----------------------------------------
Feature #8339: Introducing Geneartional Garbage Collection for CRuby/MRI
https://bugs.ruby-lang.org/issues/8339#change-39063
Author: ko1 (Koichi Sasada)
Status: Open
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: core
Target version: current: 2.1.0
| One day a Rubyist came to Koichi and said, "I understand how to improve
| CRuby's performance. We must use a generational garbage collector." Koichi
| patiently told the Rubyist the following story: "One day a Rubyist came
| to Koichi and said, 'I understand how to improve CRuby's performance..."
| [This story is an homage of an introduction in a paper:
| "A real-time garbage collector based on the lifetimes of objects"
| (by Henry Lieberman, Carl Hewitt)
| <http://dl.acm.org/citation.cfm?id=358147&CFID=321285546&CFTOKEN=10963356>]
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
--
http://bugs.ruby-lang.org/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic