New issue
Advanced search Search tips

Issue 722233 link

Starred by 4 users

Issue metadata

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



Sign in to add a comment

3.9%-25.8% regression in v8.runtimestats.browsing_mobile at 471171:471266

Project Member Reported by mlippautz@google.com, May 15 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, May 15 2017

Cc: yhirano@chromium.org
Owner: yhirano@chromium.org

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

Hi yhirano@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 : Yutaka Hirano
  Commit : 823d5c738187627cbe218f01ddac6f383bcaaba8
  Date   : Fri May 12 09:29:18 2017
  Subject: Set URLResponseBodyConsumer::kMaxNumConsumedBytesInTask to 32K

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-full-mark-compactor_max/browse_chrome/browse_chrome_omnibox
  Change       : 36.01% | 48.5983333333 -> 66.0981666667

Revision             Result                   N
chromium@471170      48.5983 +- 0.654151      6      good
chromium@471218      49.1703 +- 1.12466       6      good
chromium@471242      49.6172 +- 0.668846      6      good
chromium@471254      49.443 +- 1.0466         6      good
chromium@471256      49.5293 +- 2.16828       6      good
chromium@471257      65.3755 +- 4.32878       6      bad       <--
chromium@471260      66.3775 +- 1.8755        6      bad
chromium@471266      66.0982 +- 1.78238       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.chrome.omnibox v8.runtimestats.browsing_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979544887592134736

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5775424224755712


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!
Status: Fixed (was: Untriaged)
I reverted the change: https://chromium-review.googlesource.com/c/505649/
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, May 15 2017

Cc: bokan@chromium.org mustaq@chromium.org chaopeng@chromium.org perezju@chromium.org nedngu...@google.com
 Issue 722094  has been merged into this issue.
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, May 16 2017

Cc: lanwei@google.com
 Issue 722865  has been merged into this issue.
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, May 16 2017

 Issue 722866  has been merged into this issue.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, May 18 2017

Cc: tdres...@chromium.org
 Issue 724039  has been merged into this issue.
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, May 19 2017

 Issue 724134  has been merged into this issue.

Sign in to add a comment