pliniker / mo-gc Goto Github PK

The original design premise was flawed. However...

• replace refcounted roots with a virtual-machine stack that can be scanned
• send only new object addresses over journal
• parallelize journal reading
• implement generational write barrier
• implement incremental SSB write barrier
• throttle allocation on high rate

Performance may still be less optimal than an implementation with an integrated allocator but perhaps this still has a useful purpose in integrating a hosted language with Rust?

An integrated allocator may not need to be overly complex: Ruby appears to have fixed size slots each of which fits a union of every intrinsic type. While this may be wasteful in some situations it may be a valid first step.

Project RFC

All constructive feedback welcome:

• "this will never work because..."
• "performance will be terrible because..."
• "this would be great for..."
• "this would not work very well for..."
• likely technical hurdles
• implementation suggestions
• any clarifications needed?

The original premise was flawed. However...

• replace stack deferred reference counting with virtual machine stack scanning
• send only new object pointers over the journal
• parallelize journal processing
• implement generational write barrier
• implement incremental write barrier

Performance may still be worse than having an integrated allocator but maybe the project still has value for a hosted language?