-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apply DevTool Network/CPU throttle to FLEDGE #387
Comments
@morlovich knows a lot about the FLEDGE integration with DevTools |
So I have an idea on how to do the network part (notes below); for the CPU part, could you tell me (or screenshot if you can do it w/o any sensitive stuff) where the option is so I can chase down which devtools protocol calls it tries to make? Notes on network part: We could have AuctionURLLoaderFactoryProxy fill in the token, in which case: Alternatively the worklet process can just fill it in (passing those to lower-trust processes is OK), and we could pass it in to the worklet request stuff right at the same spot. |
Thanks. That looks to be https://chromedevtools.github.io/devtools-protocol/tot/Emulation/#method-setCPUThrottlingRate |
Network throttling will now affect Protected Audience auctions. You can find the change here. This does not include CPU throttling as that is not as easily accessible to us. |
Thank you @HabibiYou. Would you kindly please post the related Monorail link? |
We use DevTool to profile the performance of running FLEDGE auction. We were hoping to leverage the Network/CPU throttle to simulate user's experiment with lower end devices or slow internet connection. However, we noticed that those features in DevTool seems have no effect on FLEDGE network request and execution in worklets.
I think it will be very useful if Chrome can make those features apply to FLEDGE too.
The text was updated successfully, but these errors were encountered: