RE: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-04-17 Thread Chen, Li1
Hi, Hope you're doing well. We’re wondering how the experiment is progressing. Please let us know if there's anything we can do. Thanks Li From: François Doray Sent: Tuesday, March 11, 2025 2:23 AM To: blink-dev Cc: Chen, Li1 ; uazo ; blink-dev Subject: Re: [blink-dev] FYI:

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-03-10 Thread 'François Doray' via blink-dev
Hi, We will proceed with the Stable 1% experiment for this intervention. Rationale: - - The MotionMark regression is well understood. I discussed with +Camillo Bruni and we concluded that it isn't a blocker for measuring the impact of this intervention on Stable 1%. Howe

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-18 Thread Li1 Chen
https://issues.chromium.org/issues/337094888 On Friday, February 14, 2025 at 4:26:47 PM UTC+8 uazo wrote: > > We tested an intervention on Canary/Dev/Beta that reduces the frame > rate by half (e.g., from 60fps to 30fps) after 4 consecutive frames without > pixel changes. > > would it be poss

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-14 Thread uazo
> We tested an intervention on Canary/Dev/Beta that reduces the frame rate by half (e.g., from 60fps to 30fps) after 4 consecutive frames without pixel changes. would it be possible to study the changes you have made in the code? is there an associated bugid? thank you. On Wednesday, Februar

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-12 Thread Li1 Chen
Hi, We have tried Speedometer3 and MotionMark for this feature on pinpoint. Speedometer3: https://pinpoint-dot-chromeperf.appspot.com/job/11eca91ea1 https://pinpoint-dot-chromeperf.appspot.com/job/166ca91ea1 MotionMark: https://pinpoint-dot-chromeperf.appspot.com/job/11289a3ba100

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-10 Thread 'Camillo Bruni' via blink-dev
+1 to double checking the benchmark Most likely we're good as we should have at most a single idle rAF. On Fri, 7 Feb 2025 at 20:13, Johnny Stenback wrote: > Hey Francois, > > This sounds promising. My one concern is what effect(s) this might have on > our performance benchmarking work. +Camill

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-07 Thread 'Michal Mocny' via blink-dev
Very cool experiment, and happy to see positive results! Feedback RE: "no-op frames often occupy the main thread during page load or input handling"... My past experience with interactions and smoothness is that no-op-raf-loops can have more subtle effects on UX than would be predicted by just oc

Re: [blink-dev] FYI: Frame rate throttling when no frames are produced

2025-02-07 Thread Johnny Stenback
Hey Francois, This sounds promising. My one concern is what effect(s) this might have on our performance benchmarking work. +Camillo Bruni for his thoughts. We should at the very least make sure speedometer/motionmark/etc numbers are not negatively impacted by this change. Cheers, Johnny On Fri