Unless you need to keep production code up and running... TODAY. ;-)
Rodrigo Kumpera wrote: > Hi Dick, > > I believe there is very little reason to do development on libgc as sgen > is been worked and > advancing quite fast. I don't feel it's worth the risk of improving libgc. > > SGen is only a few months away from been production ready and it might > be a better idea > to spend your energy there. For example, Code to do precise marking of > managed code is > still to be done and is an area that help would be more than welcome. > > > > > > On Tue, Oct 20, 2009 at 12:44 PM, Dick Porter > <dpor...@codicesoftware.com <mailto:dpor...@codicesoftware.com>> wrote: > > Hi all > > The attached patch makes the stack marking in libgc much less > aggressive. Instead of marking every object that happens to be pointed > to by random numbers, it uses the descriptor-based scanning function > instead. > > I think this is safe for mono, as (as was pointed out to me) every > allocation has a descriptor. > > It fixes the stress-test that David posted a week or two ago, and in the > real world it allows our server to free up much more memory. It has > been tested on a production server. > > Comments? > > - Dick > > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > <mailto:Mono-devel-list@lists.ximian.com> > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list