New issue
Advanced search Search tips

Issue 787420 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 785007
Owner:
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.4%-101734.5% regression in v8.browsing_mobile at 515872:516056

Project Member Reported by mvstanton@google.com, Nov 21 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 21 2017

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

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


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

android-nexus5X
android-nexus6
android-nexus7v2
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 21 2017

Mergedinto: 785007
Status: Duplicate (was: Assigned)

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

Suspected Commit
  Author : Michael Starzinger
  Commit : 23883b85f21a2c61515cb57064b19901ae666884
  Date   : Thu Nov 09 09:31:15 2017
  Subject: [deoptimizer] Turn deopt entries into immovable Code objects.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:allocated_objects_size_avg/browse_media/browse_media_imgur
  Change       : 101628.03% | 377.581920904 -> 384106.666667

Revision                           Result                    N
chromium@515924                    377.582 +- 0.0990233      6      good
chromium@515942                    377.564 +- 0.125256       6      good
chromium@515951                    377.564 +- 0.125256       6      good
chromium@515951,v8@1ea3fd2e13      377.6 +- 0.0              6      good
chromium@515951,v8@6aa3349afb      377.582 +- 0.0990233      6      good
chromium@515951,v8@a9c908eb40      377.6 +- 0.0              6      good
chromium@515951,v8@23883b85f2      384106 +- 0.0             6      bad       <--
chromium@515951,v8@b9c9932202      384106 +- 0.0             6      bad
chromium@515951,v8@d1193e3c6c      384031 +- 259.091         6      bad
chromium@515951,v8@2328e4d196      384031 +- 259.091         6      bad
chromium@515952                    384068 +- 204.83          6      bad
chromium@515953                    384106 +- 0.0             6      bad
chromium@515954                    384106 +- 0.0             6      bad
chromium@515956                    384068 +- 204.83          6      bad
chromium@515960                    384107 +- 5.84237         6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.imgur v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Sign in to add a comment