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

Issue 759392 link

Starred by 3 users

Issue metadata

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



Sign in to add a comment

3.1%-361.4% regression in v8.runtimestats.browsing_desktop at 496971:497121

Project Member Reported by tebbi@chromium.org, Aug 27 2017

Issue description

See the link to graphs below.
 
Project Member

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

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

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


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

chromium-rel-mac11
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
Project Member

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

Cc: hablich@chromium.org
Owner: hablich@chromium.org

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

Hi hablich@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 : Michael Hablich
  Commit : f165dfdd5cb7d177de36b9fb87922ef19bb6e001
  Date   : Thu Aug 24 07:52:10 2017
  Subject: Revert "[heap] Enable concurrent marking for x86 and x64."

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : GC:duration_avg/browse_news/browse_news_flipboard
  Change       : 96.99% | 125.053 -> 246.341166667

Revision                           Result                  N
chromium@496991                    125.053 +- 17.9607      6      good
chromium@497013                    118.045 +- 14.7481      6      good
chromium@497014                    122.001 +- 18.9531      6      good
chromium@497014,v8@f165dfdd5c      250.004 +- 43.8054      6      bad       <--
chromium@497014,v8@94e1437f76      239.947 +- 8.09673      6      bad
chromium@497014,v8@237f0f3271      243.954 +- 17.2492      6      bad
chromium@497015                    249.832 +- 40.9909      6      bad
chromium@497016                    247.149 +- 12.7551      6      bad
chromium@497019                    240.956 +- 12.3433      6      bad
chromium@497024                    250.037 +- 46.7452      6      bad
chromium@497035                    246.341 +- 23.6376      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Assigned)
Project Member

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

Cc: u...@chromium.org
 Issue 760524  has been merged into this issue.
Cc: petermarshall@chromium.org
 Issue 761724  has been merged into this issue.

Sign in to add a comment