New issue
Advanced search Search tips

Issue 760513 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

10.2% regression in media.tough_video_cases_tbmv2 at 497764:497933

Project Member Reported by ulan@google.com, Aug 30 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
Project Member

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

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

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

Hi jgruber@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 : Jakob Gruber
  Commit : 3168a963ff3a85c49f4e0ef9c4e93938c22d07e6
  Date   : Mon Aug 28 11:02:27 2017
  Subject: Revert "[csa] Refactor large-object handling in string allocation"

Bisect Details
  Configuration: winx64_10_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       : 10.25% | 5115904.0 -> 5640192.0

Revision                           Result              N
chromium@497832                    5115904 +- 0.0      6      good
chromium@497844                    5115904 +- 0.0      6      good
chromium@497845                    5115904 +- 0.0      6      good
chromium@497845,v8@9b15760286      5115904 +- 0.0      6      good
chromium@497845,v8@06753c64eb      5115904 +- 0.0      6      good
chromium@497845,v8@5bd5fd45c2      5115904 +- 0.0      6      good
chromium@497845,v8@837b801666      5115904 +- 0.0      6      good
chromium@497845,v8@3168a963ff      5640192 +- 0.0      6      bad       <--
chromium@497845,v8@c65792128c      5640192 +- 0.0      6      bad
chromium@497846                    5640192 +- 0.0      6      bad
chromium@497847                    5640192 +- 0.0      6      bad
chromium@497850                    5640192 +- 0.0      6      bad
chromium@497856                    5640192 +- 0.0      6      bad
chromium@497879                    5640192 +- 0.0      6      bad
chromium@497925                    5640192 +- 0.0      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/8969839515377832304


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Aug 30 2017

Cc: dalecur...@chromium.org
 Issue 760630  has been merged into this issue.
Status: WontFix (was: Assigned)
Closing since this was a revert.

Sign in to add a comment