New issue
Advanced search Search tips

Issue 909814 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

7% regression in loading.desktop at 610945:610981

Project Member Reported by majidvp@google.com, Nov 28

Issue description

May be related to issue 909044
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=909814

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


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

mac-10_13_laptop_high_end-perf

loading.desktop - Benchmark documentation link:
  https://bit.ly/loading-benchmarks
Cc: mrsuyi@google.com
Owner: mrsuyi@google.com
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13507530140000

Introduce Timer class to clean up public attributes on __gCrWeb.findInPage. by mrsuyi@google.com
https://chromium.googlesource.com/chromium/src/+/9823151dd18b98fb46f02df511ccf1012de44598
timeToFirstContentfulPaint: 683.9 → 570.7 (-113.2)

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

Benchmark documentation link:
  https://bit.ly/loading-benchmarks
I have no idea why a change on a Js file which is iOS only will affect the performance on desktop. 
Status: WontFix (was: Assigned)

Sign in to add a comment