New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 849586 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

RuntimeCallStats Finch Experiment

Project Member Reported by cbruni@chromium.org, Jun 5 2018

Issue description

RuntimeCallStats Finch Experiment
 

Comment 1 by cbruni@chromium.org, Jun 12 2018

Cc: mpear...@chromium.org

Comment 2 by cbruni@chromium.org, Jun 12 2018

Components: Blink>JavaScript
The goal of this finch experiment is to estimate the performance and stability impact of running V8s --runtime-call-stats flag which is used in all our performance tests to gather raw internal metrics.


The ultimate goal is to possibly collect runtime call stats (RCS) for a small population of users to get a detailed understanding of how JavaScript is used in web.

In order to evaluate whether this makes sense or not we have to measure the performance and stability impact of RCS. Given that our real world benchmarks run with RCS enabled we don't expect much impact on the stability side. However we do expect a 10 to 15% performance regression with RCS enabled.

On the metric-side we're mostly interested on the impact on the V8 metrics (V8.Compile, V8.Execute) and probably some startup metrics.

Comment 3 by cbruni@chromium.org, Jun 12 2018

Cc: jochen@chromium.org hpayer@chromium.org
FYI, for the "ultimate goal" (collecting new data from users), that would likely require a launch bug and commensurate privacy review.  (It depends on what you're collecting.)  Simply seeing whether enabling this flag slows down Chrome is fine for this as a non-launch bug.

Comment 5 by cbruni@chromium.org, Jun 14 2018

SGTM. Given that we will collect more detailed information on where you spend time in the VM we have to think about potential privacy issues.

Sign in to add a comment