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

Issue 759588 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
█ kraynov@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

102.5% regression in loading.desktop at 495263:495450

Project Member Reported by kraynov@chromium.org, Aug 28 2017 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 28 2017 

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

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


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

chromium-rel-mac-retina
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 28 2017 


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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/Naver

Revision             Result                  N
chromium@495262      482.248 +- 1014.74      21      good
chromium@495450      526.005 +- 1037.85      21      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=Naver loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Comment 4 by sullivan@chromium.org, Oct 9 2017

Status: WontFix (was: Untriaged)
This came back down.
►

Sign in to add a comment