>> > Ah. Then I feel a bit better, because it's my mistake rather than theirs. > No contention exists for allocation purposes, but I'm now convinced that > references *can* leak across nurseries. In RC-immix, this isn't an issue > because mutators and collectors are not permitted to overlap. This allows > objects to be relocated cleanly. >
How is mutators and collectors not overlappign diffirent from a stop the world ? > >> Yes thats the problem but why do we care ? 90% of apps just set a big >> Nursery and who cares about the global pause, For the remaining 10% set a >> small ( or no) nursery so the pause is tiny ( or better yet partial >> sweeps as you mentioned so new objects can die). >> > > Getting rid of the pause from the tenured heap is not that big a > challenge. The challenge is to make sure that a short pause for *my* nursery > doesn't require *your* thread to stop. > Everything has stop the world pauses for root scans so the issue is not my nusery stop your thread but how long it stops your thread .. and obviously for URC this is bounded by the nursery size .. down to zero nursery. > > I disagree. I agree that we don't have to *implement* the world's > fanciest concurrent collector right now. But we need to know that such a > collector is *possible*. > Im already convinced you can get low global pauses with just ref counting at a 10% cost (with modern techniques) .. Which is good enough for me.. Its a mistake to get a fast and low pause in the same collector. Ben
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
