New issue
Advanced search Search tips

Issue 784378 link

Starred by 1 user
Status: WontFix
Owner:
asvitk...@chromium.org
Closed: Jan 2018
Cc:
m...@chromium.org
dtu@chromium.org
tdresser@google.com
mattm@chromium.org
asvitk...@chromium.org
mark@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.1%-316.2% regression in loading.desktop at 515193:515449

Project Member Reported by tdres...@chromium.org, Nov 13 2017 
See the link to graphs below.
Project Member

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

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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac12
chromium-rel-win7-x64-dual
win-high-dpi
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Nov 13 2017 


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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/warm/Naver

Revision             Result                  N
chromium@515252      582.322 +- 1542.24      21      good
chromium@515373      749.345 +- 1211.75      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --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/8963033819433748800


For feedback, file a bug with component Speed>Bisection
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/15b12969f80000
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14dde499f80000
Project Member

Comment 9 by 42576172...@developer.gserviceaccount.com, Nov 14 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/16da795ef80000
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Nov 15 2017 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12952395f80000

Comment 12 by sullivan@chromium.org, Jan 12 2018

Cc: dtu@chromium.org
dtu: the charts in pinpoint look like there is a regression, but it's super noisy. Any ideas?

Comment 13 by dtu@chromium.org, Jan 12 2018 

The algorithm has changed since then. Let me kick off a new one.
Project Member

Comment 15 by 42576172...@developer.gserviceaccount.com, Jan 12 2018 

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14bd996f040000

Comment 16 by sullivan@chromium.org, Jan 25 2018

Status: WontFix (was: Untriaged)
tdresser: Another first paint regression that Bisect can't repro that recovered.

Comment 17 by dtu@chromium.org, Jan 25 2018 

Hmm, I was expecting a repro with that last job. I noticed just now the previous job had a wider range. I'm going to kick off one more.
Project Member

Comment 19 by 42576172...@developer.gserviceaccount.com, Jan 26 2018

Cc: mark@chromium.org asvitk...@chromium.org m...@chromium.org mattm@chromium.org
Owner: asvitk...@chromium.org
Status: Assigned (was: WontFix)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11e02122840000

Re-land "Switch Mac to use time_exploded_posix.cc."
By asvitkine@chromium.org · Fri Nov 10 00:38:46 2017
chromium @ af2ab97d5f8900c802fe6a20e726c4f4b8392228

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Comment 20 by asvitk...@chromium.org, Jan 26 2018

Status: WontFix (was: Assigned)
WontFix, I dug into this already here, see the explanation:

https://bugs.chromium.org/p/chromium/issues/detail?id=784381#c17
►

Sign in to add a comment