responding before 50ms deadline about turtledove

[JensenPaul]

I assume when you say 50ms that you’re referring to the default perBuyerTimeout. Before I answer your question, I want to point out that our current recommendation is for sellers to prefer using perBuyerCumulativeTimeout over perBuyerTimeout, so sellers following this advice are likely setting perBuyerTimeout to a value much higher than 50ms and relying instead on perBuyerCumulativeTimeout. In this case, buyers are incentivized to respond as soon as possible in each generateBid() invocation in order to leave time for their other interest groups’ generateBid() invocations to complete before the perBuyerCumulativeTimeout expires.

In the case that a seller is not following our recommendation and is instead relying on the default perBuyerTimeout, then they may still be using an overall auction timeout via the AbortSignal mechanism, in which case buyers are incentivized to respond promptly to avoid hitting the overall timeout.

In regards to your question “will the PAAPI auction runner wait till 50 ms are up before collecting responses?”, Protected Audience auctions following the default 50ms perBuyerTimeout will stop individual generateBid() invocations after 50ms, which ignores any unreturned bids, however bids submitted by setBid() will still be used.

@dtd1555, would you mind adding your full name to your GitHub profile?

[JensenPaul]

There is no limit on the number of times setBid() can be called.

[dtd1555]

Thanks @JensenPaul, that is very helpful. Would you mind answering a follow up question - is there a limit on the number of times setBid() can be called?
Updated my profile :)