New issue
Advanced search Search tips

Issue 681036 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

3% regression in speedometer at 443389:443443

Project Member Reported by nzolghadr@chromium.org, Jan 13 2017

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=681036

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


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

android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jan 14 2017

Cc: jkummerow@chromium.org
Owner: jkummerow@chromium.org

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

Hi jkummerow@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 : jkummerow
  Commit : b4654bf30e63499dd689472bcfde7fbf8c7484c7
  Date   : Thu Jan 12 15:00:19 2017
  Subject: Revert of Internalize strings in-place (patchset #20 id:380001 of https://codereview.chromium.org/2549773002/ )

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : speedometer
  Metric       : Total/Total
  Change       : 2.82% | 28683.2283333 -> 29492.9269444

Revision                           Result                  N
chromium@443389                    28683.2 +- 384.282      6       good
chromium@443396                    28870.6 +- 397.455      6       good
chromium@443400                    28807.0 +- 605.669      14      good
chromium@443400,v8@aa75904e3c      28724.6 +- 84.2359      3       good
chromium@443400,v8@b4654bf30e      29696.8 +- 624.458      14      bad       <--
chromium@443400,v8@ee2f07b677      29673.9 +- 518.84       14      bad
chromium@443400,v8@aff64e9dfa      29595.3 +- 551.969      14      bad
chromium@443400,v8@53137df89a      29646.7 +- 591.799      14      bad
chromium@443401                    29539.9 +- 556.891      14      bad
chromium@443402                    29616.2 +- 494.63       6       bad
chromium@443403                    29616.8 +- 466.42       6       bad
chromium@443416                    29705.8 +- 335.841      6       bad
chromium@443443                    29492.9 +- 386.838      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 speedometer

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

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


| 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 Tests>AutoBisect.  Thank you!
Status: Assigned (was: Untriaged)
This bug has an owner, but was in a state that our triage picked up. Marking as Assigned.
Owner: ----
Status: Available (was: Assigned)
Bisect is bogus, the supposed culprit wasn't even in the range (it had been hand-picked into the previous V8 roll).
Status: WontFix (was: Available)

Sign in to add a comment