-
Notifications
You must be signed in to change notification settings - Fork 232
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
Top level seller timeout values aren't available to the component sellers #1059
Comments
Top-level seller timeouts don't currently apply to component sellers or buyers - they only affect the top-level auction (which means just the top-level seller's scoreAd()). |
@MattMenke2 I updated the description. Pl lmk if that doesn't make sense |
"as these timeouts must be less than or equal to those of the top-level seller (or risk timing out).". The top-level seller's auctionConfig timeouts aren't applied to the component auction. I think, from offline conversation, you actually mean some non-PA timeout applied to the entire auction? |
Based on your comment, seems like the two timeout values aren't related. Is there another timeout value that is applied to the entire PA auction? If the top level seller timeout is configured to be 50ms and the component seller configures the perbuyertimeout to be 1000ms, in the current scheme of things, will the top level auction not run until all generatebids and component seller's scoread are run i.e. 1000ms per ig, per ssp? |
No, there's currently no timeout that can be applied to the entire auction. It might be nice to add one - then a result of a partially completed auction could be run, which aborting an auction won't let you do. Which top-level seller timeout? There are 3 timeouts, currently:
I think it would be reasonable to consider adding more timeouts (e.g., whole auction timeout, script or signals fetch timeouts, etc) and/or make top-level auction timeouts apply to component auctions. If adding new timeouts we should try to figure out the minimum set that would help, though. |
The SSPs/component sellers need to understand the top-level seller timeouts when developing the component auctionConfig, as these timeouts must be less than or equal to those of the top-level seller (or risk timing out).
Top level seller timeouts are not provided in an automated way via Chrome or other instrumentation. The component seller is unable to programmatically know this value when creating auctionConfigs.
The text was updated successfully, but these errors were encountered: