New issue
Advanced search Search tips

Issue 875365 link

Starred by 1 user
Status: Duplicate
Merged: issue 875367
Owner: ----
Closed: Oct 4
Cc:
tdres...@chromium.org
oysteine@google.com
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.5%-18% regression in timeToFirstContentfulPaint,timeToFirstMeaningfulPaint at 581928:582102

Project Member Reported by 42576172...@developer.gserviceaccount.com, Aug 17 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 17 

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 17

Cc: oysteine@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/10369ada640000

Enable Perfetto usage for the loading perf tests. by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/49a68554cf5658d0cc3741a89db2fca1380a6fcc
222.7 → 249.9 (+27.19)

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

Comment 4 by eseckler@chromium.org, Oct 4

Mergedinto: 875367
Status: Duplicate (was: Assigned)
►

Sign in to add a comment