|OriginTrial desktop last||102|
|OriginTrial desktop first||101|
|DevTrial on desktop||101|
|OriginTrial android last||102|
|OriginTrial android first||101|
|DevTrial on android||101|
What's the plan for finding sites this breaks? Monitor bug reports? Or is there something more proactive we could do?
Thanks!What's the plan for finding sites this breaks? Monitor bug reports? Or is there something more proactive we could do?I'm thinking about bug reports and guardian metrics. shaseley@ might have additional insight from running a similar experiment crbug.com/1263190
I'm sharing an update with results of the experiments over 21 days on Chrome Beta M102.
The results below are mostly small percentages changes, and the finch guidelines says to trust results on Stable. Given no issue have been raised AFAIK I would like to roll out a 1% finch experiment on Stable and I'm wondering what would be the required steps to do this (besides flipping boxes on the launch crbug.com/1298967) without amending what the spec says just yet.
The experiment MaxUnthrottledTimeoutNestingLevel has been running on canary/dev/beta M101 and M102.
Another experiment SetTimeoutZeroWithoutClamping which removes setTimeout(,0) clamping to 1 ms is running at Enabled(25%) and Default(50%) on Beta. Analyzing the results for both experiments together makes sense because our goal is to avoid delayed tasks for immediate setTimeout()s.
MaxUnthrottledTimeoutNestingLevel (50% enabled / 50% control) + SetTimeoutZeroWithoutClamping (Default + Enabled is 75%)
No impact on Guiding Metrics
-15.85% Time To Paint For Each Ad Frame @ 95%ile 2-diamonds
-1.78% First Input Delay @ 99%ile 1-diamonds
-0.74% Time to Largest Contentful Paint @ 99%ile 1-diamonds
-0.79% Cumulative Layout Shift @ 95%ile 2-diamonds
-1.45 / 1.26% Startup Time @ 95 / 99%ile 1 / 2-diamonds
+1.93% Scroll Latency Count 1-diamonds
+0.32% Memory: Renderer@ 50%ile 1-diamonds
MaxUnthrottledTimeoutNestingLevel ignoring SetTimeoutZeroWithoutClamping
Note: Results here are less interesting since our goal is to avoid delayed tasks for immediate setTimeout()s, which is only achieved under SetTimeoutZeroWithoutClamping.
+1.73% Time to First Contentful Paint @ 95%ile 2-diamonds
-1.28% Frame Drawing Interval @ 95%ile 1-diamonds
-1.44% Startup Time @ 99%ile 1-diamonds
Note: the downside of experimenting on Stable is that the intersection of both 1% experiments is very small and we probably won't be able to analyze results alongside before SetTimeoutZeroWithoutClamping ships (this should happen soon though).
Maybe a console warning message if we hit the nesting level that we plan to increase? I'm not sure how effective that would be in helping get folks to try it.