Trace scavenger throughput.

Trace scavenger throughput.

BUG=
R=hpayer@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=23195

[ulan, 2014-08-19 10:09:13]

PTAL

[Hannes Payer (out of office), 2014-08-19 11:52:59]

https://codereview.chromium.org/487753003/diff/20001/src/heap/gc-tracer.cc
File src/heap/gc-tracer.cc (right):

https://codereview.chromium.org/487753003/diff/20001/src/heap/gc-tracer.cc#ne...
src/heap/gc-tracer.cc:107: heap_->new_space()->top() -
heap_->new_space()->bottom();
The question here is: What is the right size we care about? We have to correlate
the time spent in scavenging with some size.

The Scavenger will process live objects in to space and in from space.
I think we should account for both spaces. WDYT?

[Hannes Payer (out of office), 2014-08-19 11:58:57]

As discussed offline, you are already accounting for both kinds of objects in
the new space since you look at the new space at the beginning of the scavenger.

LGTM

[ulan, 2014-08-19 12:08:04]

Committed patchset #2 manually as 23195 (presubmit successful).