New issue
Advanced search Search tips

Issue 778667 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

4.1% improvement in speedometer at 510495:510578

Project Member Reported by jarin@google.com, Oct 26 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 26 2017

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

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


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

chromium-rel-win8-dual
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 27 2017

Cc: bmeu...@chromium.org
Owner: bmeu...@chromium.org

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

Hi bmeurer@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 : Benedikt Meurer
  Commit : d5c19aa9fc536638b4d3831ba01cf0f1a6a05bbe
  Date   : Fri Oct 20 12:16:10 2017
  Subject: [ic] Ensure that we make progress on KeyedLoadIC polymorphic name.

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : speedometer
  Metric       : BackboneJS-TodoMVC/BackboneJS-TodoMVC
  Change       : 2.96% | 312.234833333 -> 303.000416667

Revision                           Result                  N
chromium@510494                    312.235 +- 1.97331      6      good
chromium@510536                    310.647 +- 1.67433      6      good
chromium@510557                    311.076 +- 2.38556      6      good
chromium@510560                    310.238 +- 2.73388      6      good
chromium@510562                    311.47 +- 2.47127       6      good
chromium@510562,v8@035b4ccfc9      310.631 +- 3.61448      6      good
chromium@510562,v8@4cb88e3ab4      311.737 +- 2.63727      6      good
chromium@510562,v8@d5c19aa9fc      302.195 +- 3.56857      6      bad       <--
chromium@510563                    302.955 +- 2.4305       6      bad
chromium@510568                    304.634 +- 6.0305       6      bad
chromium@510578                    303.0 +- 3.80616        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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection
Status: WontFix (was: Assigned)
Infrastructure is confused here. The performance actually improves.

Sign in to add a comment