On 2014/07/14 15:04:39, Hannes Payer wrote:
I think the problem with the tracer is that it holds the state of three
different gc subsystems. This is a mess. Maybe we should have three tracer
instances: scavenger, mark-compact, and marking-steps. WDYT? Based on
that we
can also keep a history of events for each subsystem and can simply query
the
given instance.
Per offline discussion, we want to separate tracing of scavenger,
mark-compact,
and marking-steps. We also want to make sure that stats use purely for
debugging
and profiling are separated from what we use to drive our heuristics
(without
duplicating code or measurements). I'll close this CL now and start a new
one,
cleaning up the existing GCTracer as a first step.
https://codereview.chromium.org/390823003/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
