New issue
Advanced search Search tips

Issue 855784 link

Starred by 2 users
Status: Assigned
Owner:
sclit...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Consider enabling lazy frame visible load time metrics gathering by default

Project Member Reported by sclit...@chromium.org, Jun 22 2018 
There are worries that this will have a non-zero performance cost, but we should actually measure if this is significant or not, and turn it on by default if the perf differences aren't significant.
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jun 23 2018 

📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/142209ab240000
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Jun 23 2018 

📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/16c6301f240000
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Jun 23 2018 

📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/12b5bb17240000
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Jun 26 2018 

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14825f2f240000

The swarming task expired. The bots are likely overloaded, dead, or misconfigured.
►

Sign in to add a comment