New issue
Advanced search Search tips

Issue 758101 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1%-10.2% regression in media.tough_video_cases_tbmv2 at 495855:496002

Project Member Reported by mlippautz@chromium.org, Aug 23 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 23 2017

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=758101

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=e225d957985d485ecf06ca49eb71916202b58acc61b909c85e87b7ac71bf4128


Bot(s) for this bug's original alert(s):

chromium-rel-mac11
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 23 2017

Cc: marja@chromium.org
Owner: marja@chromium.org
Status: Assigned (was: Untriaged)

=== Auto-CCing suspected CL author marja@chromium.org ===

Hi marja@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Marja Hölttä
  Commit : 0d14ae178113539e76c4733f73ad8197f18427f4
  Date   : Mon Aug 21 10:34:39 2017
  Subject: Revert "Revert "Revert "[parser] FLAG_aggressive_lazy_functions = true for a test run."""

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/video.html?src_crowd1080.mp4
  Change       : 8.54% | 5115904.0 -> 5552810.66667

Revision                           Result                 N
chromium@495854                    5115904 +- 0.0         6      good
chromium@495928                    5115904 +- 0.0         6      good
chromium@495933                    5115904 +- 0.0         6      good
chromium@495935                    5115904 +- 0.0         6      good
chromium@495935,v8@87613860c6      5115904 +- 0.0         6      good
chromium@495935,v8@895356129e      5115904 +- 0.0         6      good
chromium@495935,v8@0d14ae1781      5552811 +- 478607      6      bad       <--
chromium@495936                    5552811 +- 478607      6      bad
chromium@495938                    5552811 +- 478607      6      bad
chromium@495947                    5640192 +- 0.0         6      bad
chromium@495965                    5552811 +- 478607      6      bad
chromium@496002                    5552811 +- 478607      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.crowd1080.mp4 media.tough_video_cases_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970483949749201264


For feedback, file a bug with component Speed>Bisection

Comment 4 by marja@chromium.org, Aug 23 2017

Status: WontFix (was: Assigned)
The "regressing" commit is a revert which ends an experiment by flipping a flag back to false. So I'm not going to do anything about this regression. The flag improves some sites and regresses some other sites, and so does the revert.
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Aug 23 2017

Cc: chcunningham@chromium.org
 Issue 758328  has been merged into this issue.

Sign in to add a comment