At Thu, 3 Sep 2015 11:12:50 +0100, Tim Brown wrote: > On 28/08/15 20:02, Matthew Flatt wrote: > > I think the sandbox is relevant because `sandbox-memory-limit` remains > > in effect (even though you're disabling the per-evaluation limit by > > setting `sandbox-eval-limits`). A sandbox memory limit triggers memory > > accounting in the GC. I see that memory accounting in the GC has a > > problem with places, and I can provoke a crash by targeting that > > problem directly. > > Out of interest - is there much overhead in having memory accounting > active in the GC? > > I can’t avoid it, since I’ll be using sandboxes... > but is there any idea of the cost?
Memory accounting increases the cost of a major GC by about 25%. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
