[#144] Another implementation of Bignum — "Dmitry Antipov" <dmitry.antipov@...>
Hello Ruby hackers,
15 messages
2002/06/06
[#151] Re: Another implementation of Bignum [tarball attached]
— "Dmitry Antipov" <dmitry.antipov@...>
2002/06/07
Hello again,
[#152] Re: Another implementation of Bignum [tarball attached]
— matz@... (Yukihiro Matsumoto)
2002/06/07
Hi,
[#174] Improving Ruby's garbage collector for interactive apps — Matthew Bloch <mattbee@...>
re: this problem I had a few weeks back:
8 messages
2002/06/19
[#177] Re: Improving Ruby's garbage collector for interactive apps
— matz@... (Yukihiro Matsumoto)
2002/06/20
Hi,
[#178] Re: Improving Ruby's garbage collector for interactive apps
— Matthew Bloch <mattbee@...>
2002/06/21
On Thursday 20 June 2002 18:54, you wrote:
[#186] Steps to get multiple interpreters per process... — Sean Chittenden <sean@...>
Can someone chart out what would need to happen to get multiple ruby
10 messages
2002/06/24
[#187] Re: Steps to get multiple interpreters per process...
— matz@... (Yukihiro Matsumoto)
2002/06/25
Hi,
[#188] Re: Steps to get multiple interpreters per process...
— Sean Chittenden <sean@...>
2002/06/25
> |Can someone chart out what would need to happen to get multiple
[#191] Re: Steps to get multiple interpreters per process...
— Chris Ross <chris@...>
2002/06/25
Re: Improving Ruby's garbage collector for interactive apps
From:
matz@... (Yukihiro Matsumoto)
Date:
2002-06-21 03:29:10 UTC
List:
ruby-core #179
Hi,
In message "Re: Improving Ruby's garbage collector for interactive apps"
on 02/06/21, Matthew Bloch <mattbee@soup-kitchen.net> writes:
|> Yes and yes. Generational mark and sweep algorithm was done before,
|> but it was not good enough, probably due to write barrior cost.
|
|Which algorithm in particular, and how was the barrier implemented? Did you
|use OS page protection or catch it at application level?
It's based on linked generations, and the barrier was implemented by
application level. OS page protection is not portable.
Long time ago, before I implemented Ruby's own GC, I tried to use
Boehm GC, but it dumped core immediately. The situation might have
changed in the last 9 years.
Upon recent CPU power / memory size situation, the simplest GC scheme
rarely cause problems, except when too many objects are allocated.
Am I too optimistic?
matz.