V8 uses background tasks in the garbage collector and the compiler.
Currently time spent in background tasks is not accounted and is not tracked in telemetry performance benchmarks.
A metric that tracks time in background tasks would help us see the performance trade-offs and the overhead of concurrency.
Thanks, Ross!
Looks like each background parsing task maintains its own local RCS table, which is then joined to the main thread RCS table?
https://cs.chromium.org/chromium/src/v8/src/parsing/parse-info.cc?rcl=20961d2635086f3c5bee27f2c72ccf0975003d96&l=159
I think that would work for GC too.
I am wondering if we can avoid manual management of local RCS tables by directly emitting trace-events from the background tasks and then aggregating those events in the metric.
Comment 1 by u...@chromium.org
, Aug 23 2017