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

Issue 718797 link

Starred by 2 users
Status: Fixed
Owner:
█ wiktorg@google.com
Email to this user bounced
Closed: Jun 2017
Cc:
cbruni@chromium.org
█ wiktorg@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

17.1% regression in v8.runtimestats.browsing_mobile_classic at 468623:469134

Project Member Reported by verwa...@chromium.org, May 5 2017 
See the link to graphs below.

Comment 1 by verwa...@chromium.org, May 5 2017 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgitKzsgoM


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

android-webview-nexus5X
Project Member

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


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Total:duration_avg/browse_social/browse_social_facebook


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

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

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


| 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!

Comment 5 by danno@chromium.org, May 7 2017

Cc: -verwa...@chromium.org cbruni@chromium.org
Owner: verwa...@chromium.org
Status: Assigned (was: Untriaged)
Toon, is this worth tracking down? If not, please close.
Project Member

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


=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Total:duration_avg/browse_social/browse_social_facebook


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

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

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


| 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!
Project Member

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

Cc: wiktorg@google.com
Owner: wiktorg@google.com

=== Auto-CCing suspected CL author wiktorg@google.com ===

Hi wiktorg@google.com, 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 : Wiktor Garbacz
  Commit : 00912d73f1a83f16b6e7f88bf4837d5a7a8dc857
  Date   : Tue May 02 09:44:20 2017
  Subject: [parser] Inital parallel parse tasks implementation.

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : v8.runtime_stats.top_25
  Metric       : Compile:duration_avg/https___www.linkedin.com_m_
  Change       : 11.00% | 116.7025 -> 129.109111111

Revision                           Result                  N
chromium@468615                    116.703 +- 6.84347      14      good
chromium@468635                    116.69 +- 6.63631       14      good
chromium@468640                    115.849 +- 3.93547      9       good
chromium@468643                    117.03 +- 4.35694       14      good
chromium@468643,v8@34e7945647      116.732 +- 3.24045      7       good
chromium@468643,v8@a39a833ad3      116.471 +- 1.90424      5       good
chromium@468643,v8@00912d73f1      130.058 +- 4.41         6       bad       <--
chromium@468643,v8@b8e9bd4051      130.14 +- 3.2712        5       bad
chromium@468644                    130.474 +- 3.51972      5       bad
chromium@468645                    131.057 +- 4.13659      4       bad
chromium@468654                    129.621 +- 2.23226      3       bad
chromium@468692                    129.334 +- 1.96134      4       bad
chromium@468768                    130.11 +- 2.78708       3       bad
chromium@468921                    131.109 +- 2.06434      4       bad
chromium@469227                    129.109 +- 5.24659      9       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=https...www.linkedin.com.m. v8.runtime_stats.top_25

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

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


| 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!
Project Member

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


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Blink C++:duration_avg/browse_social/browse_social_facebook

Revision             Result                  N
chromium@468609      2063.39 +- 617.208      21      good
chromium@469185      2159.37 +- 642.558      21      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.social.facebook v8.runtimestats.browsing_mobile_classic

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

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


| 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!
Project Member

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


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile_classic
  Metric       : Blink C++:duration_avg/browse_social/browse_social_facebook

Revision             Result                 N
chromium@468609      2142.2 +- 656.506      21      good
chromium@469185      2105.2 +- 418.556      21      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.social.facebook v8.runtimestats.browsing_mobile_classic

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

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


| 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!

Comment 13 by marja@chromium.org, Jun 8 2017

Status: Fixed (was: Assigned)
Closing this since the commit was reverted (for other reasons).
►

Sign in to add a comment