Ojan, I thought the DOMperf testing framework that we developed does a lot of the work to help compensate (or at least illustrate) variability due to GC. I thought there was more of a push to start using this for new benchmarks as well. Is there a reason why that doesn't work for your case?
Erik On Thu, Aug 26, 2010 at 8:43 AM, Ojan Vafai <[email protected]> wrote: > On Thu, Aug 26, 2010 at 1:14 AM, Mads Ager <[email protected]> wrote: > >> I think the main issue here is >> that in order to get rid of DOM wrappers in the heap you need more >> than one GC (at least two - one to notice that it is not referenced >> from JS and perform a callback and another one to actually get rid of >> the object). Does it help if you do a couple of calls to collect()? > > > Doing a couple calls just feels a bit imprecise, but it's not a big deal. > I'll do three I guess. > > Thanks, > Ojan > > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
