New issue
Advanced search Search tips

Issue 705476 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 698746


Participants' hotlists:
I-TF-Launch


Sign in to add a comment

'Classic' benchmarking configuration doesn't seem to be disabling I+TF

Project Member Reported by rmcilroy@chromium.org, Mar 27 2017

Issue description

Michael, the -classic benchmark configuration doesn't seem to be disabling Ignition+Turbofan. If you look at the following graphs, -classic follows identically with the (currently I+TF) default pipeline. This shouldn't be the case (notice the big drops in each graph when I+TF was enabled).

Could you take a look?
 
Owner: mythria@chromium.org
Status: Started (was: Untriaged)
Ross and me took a look into this. Passing --no-turbo to chrome does not disable Turbofan. So currently classic is running the same configuration as the default (Ignition + TurboFan). It could be because of the --future flag that is set later. I will look into it today. 
Cc: hablich@chromium.org
Owner: rmcilroy@chromium.org
Status: Available (was: Started)
This is because of the V8Future configuration. After these cls:  https://codereview.chromium.org/2747163004/ and  https://codereview.chromium.org/2744293002/ V8Future will be enabled which enables --turbo. This happens after processing the command line flags, so --no-turbo does not have the intended affect. 

Ross would look into it by reverting the cls after setting up stabile finch trials.
Sorry was/am sick. Thanks for catching and starting to resolving it. 
Blocking: 698746
Project Member

Comment 6 by bugdroid1@chromium.org, Mar 29 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/124254af04fd234fffa434b8b4380f5056528e3b

commit 124254af04fd234fffa434b8b4380f5056528e3b
Author: rmcilroy <rmcilroy@chromium.org>
Date: Wed Mar 29 14:30:55 2017

Remove V8Future experiment.

Removes the V8 Future experiment since it conflicts with the V8NoTurbo
experiment and adds confusion as to how to enable / disable Ignition+
TurboFan.

Also make the description for the V8NoTurbo about://flags entry clearer.

BUG=chromium:703569, chromium:705476 

Review-Url: https://codereview.chromium.org/2786633002
Cr-Commit-Position: refs/heads/master@{#460380}

[modify] https://crrev.com/124254af04fd234fffa434b8b4380f5056528e3b/chrome/browser/about_flags.cc
[modify] https://crrev.com/124254af04fd234fffa434b8b4380f5056528e3b/chrome/browser/flag_descriptions.cc
[modify] https://crrev.com/124254af04fd234fffa434b8b4380f5056528e3b/gin/gin_features.cc
[modify] https://crrev.com/124254af04fd234fffa434b8b4380f5056528e3b/gin/public/gin_features.h
[modify] https://crrev.com/124254af04fd234fffa434b8b4380f5056528e3b/gin/v8_initializer.cc

Status: Fixed (was: Available)

Sign in to add a comment