AW: [Mono-devel-list] GC/Memory allocation performance

[Varga Zoltan]

                                            Hi,

  During incremental GC, the heap is write protected, which
causes
system calls like read() to fail if they get passed a
pointer to memory
inside the heap. This happens in the current io-layer code.
Even if
this is fixed, enabling incremental GC only shortens GC
pauses, but
leads to longer total time spent doing GC. 

            bye

                      Zoltan


Paolo Molaro <lupus at ximian.com> írta:

> On 05/30/03 Marcus wrote:
> > Doesn't Boehm's GC have a compacting mode? I know that
SRC Modula-3 (and its 
> > descendants) for over 10 years have used a Boehm GC that
is generational, 
> > incremental, and compacting.
> 
> The standard Boehm GC can do some form of
incremental/generational
> collectiong (but no compacting), but enabling it in mono
always results
> in a SEGV in libgc's code for me. It may still be a mono
issue, I didn't
> investigate it. That support also relies on trapping
SIGSEGV that mono
> uses too to handle null ref exceptions, so it may not be
possible to
> deal with it anyway.
> Enabling it for the C microbenchmark makes the numbers
worse, though,
> from 0.95 to 1.2 for the statically compiled version.
> 
> lupus
> 
> -- 
>
-----------------------------------------------------------------
> lupus at debian.org                                    
debian/rules
> lupus at ximian.com                             Monkeys do it
better
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
>