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

Issue 865433 link

Starred by 1 user

Issue metadata

Status: Started
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Scheduler: Experiment with de-prioritizing tasks posted by different types of frames.

Project Member Reported by farahcharab@chromium.org, Jul 19

Issue description

Run the following experiments on Beta. 

1- De-prioritize hidden frame tasks to low priority. 
2- De-prioritize subframe tasks to low priority during loading.
3- De-prioritize throttleable tasks to low priority during loading. 
4- De-prioritize subframe throttleable tasks to low priority.
5- De-prioritize ad frames to low priority. 
6- De-prioritize ad frames to low priority during loading.
7- De-prioritize background pages to low priority.  

All of these experiments were run on Canary/Dev. Experiments 1,2,3 seem to have a good impact on our loading metrics for low memory devices. Here are the results for the first four experiments on Canary/Dev:

https://uma.googleplex.com/p/chrome/variations/?sid=d1e5079dae6b66abfa1892f4a85a991c

The last experiment isn't have any good impact, and we are interested in running it on Beta as well to get a better understanding of why is this happening.


 
Status: Started (was: Untriaged)

Sign in to add a comment