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

Issue 670256 link

Starred by 1 user
Status: Duplicate
Merged: issue 756396
Owner:
█ nasko@chromium.org
Out until 24 Jan
Closed: Aug 2017
Cc:
wfh@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 670076



Sign in to add a comment

Turning down OOPIF telemetry benchmark once OOPIF is fully launched

Project Member Reported by nedngu...@google.com, Dec 1 2016 
This bug is for tracking turning down OOPIF telemetry benchmark once the project is fully launched.

Comment 1 by nasko@chromium.org, Dec 1 2016 

This sounds good. However, we will have to add some flavor of OOPIFs into the main benchmarks to ensure there is visibility into potential regressions.

Comment 2 by nedngu...@google.com, Dec 1 2016 

SG. Seems like the action item is ensure the system health (core) benchmark has use cases that cover OOPIFs

Comment 3 by nedngu...@google.com, Dec 1 2016 

nasko: how do we know if a site would trigger OOPIF?

Comment 4 by nedngu...@google.com, Aug 31 2017

Mergedinto: 756396
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment