New issue
Advanced search Search tips

Issue 788411 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

76.2% regression in rasterize_and_record_micro.top_25 at 518183:518253

Project Member Reported by hjd@google.com, Nov 24 2017

Issue description

See the link to graphs below.
 
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 24 2017

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

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


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

android-webview-nexus5X

Comment 4 by hjd@chromium.org, Dec 5 2017

Kicked bisect.

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : rasterize_and_record_micro.top_25
  Metric       : rasterize_time/file___static_top_25_gmail.html

Revision             Result                  N
chromium@518182      22.021 +- 2.93384       21      good
chromium@518253      22.4779 +- 3.05476      21      bad

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=file...static.top.25.gmail.html rasterize_and_record_micro.top_25

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

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


For feedback, file a bug with component Speed>Bisection
Trying another bisect now that pinpoint can show us, but it really looks like this metric is bimodal.
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jan 22 2018

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/128f8ee8840000
Cc: dtu@chromium.org sullivan@chromium.org simonhatch@chromium.org vmp...@chromium.org
Status: WontFix (was: Untriaged)
+vmpstr: WontFix-ing this because AFIACT this isn't a real regression, metric looks bimodal.

+simonhatch, dtu: last bisect didn't produce values. Shouldn't pinpoint be able to produce values if the old bisect in #5 could?
I *think* this was the gitiles issue, based on the date and that the new jobs should get further.

Sign in to add a comment