The three schemes currently implemented are generational, stop-the-world
mark-and-sweep, and incremental mark-and-sweep. The generational GC
implementation is not complete yet. The default GC scheme at the moment
is stop-the-world mark-and-sweep. For the 1.0 release the default will
likely be either incremental or generational, depending on which proves
to be the most stable and best performance on average across common use
cases.
We will definitively need good documentation for this part:
- Parrot VM tuning, is it needed, why and when ?
- Parrot and JVM, a simple face-to-face comparative description will
help a lot of folks coming from Java land and as well sysadmins which
are maintaining the JVM options for app servers, for instance. For
instance, this would be very interesting how Parrot VM will be
configured to run Perl 6...
- Parrot's VM options should try to stay as a small set, good
documented and not expand in dozens hard to maintain and hard to understand.
Thanks for message,
Stefan
