Commit-Queue | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
I think we need a higher level integration test to ensure that we correctly run auctions. I'm particularly concerned about interactions with the multi-threaded bidding feature.
fresh_context_recycler = std::move(unused_context_recyclers_.back());
How do we ensure that the context is associated with the current thread?
size_t thread_index = next_thread_index_;
I don't understand how this works with multiple bidder threads. It looks like all of the contexts we create are tied to a single thread. That's not ideal, given we try to spread the load over all threads.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
I think we need a higher level integration test to ensure that we correctly run auctions. I'm particularly concerned about interactions with the multi-threaded bidding feature.
Good idea -- do you think it's sufficient for me to make the unittests subclass
BidderWorkletMultiThreadingTest instead BidderWorkletTest?
fresh_context_recycler = std::move(unused_context_recyclers_.back());
How do we ensure that the context is associated with the current thread?
unused_context_recyclers_ is a member of V8State which we always run with the same associated v8_runner.
size_t thread_index = next_thread_index_;
I don't understand how this works with multiple bidder threads. It looks like all of the contexts we create are tied to a single thread. That's not ideal, given we try to spread the load over all threads.
I increment thread_index in the for loop, so the load is spread over all the threads.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Abigail KatcoffI think we need a higher level integration test to ensure that we correctly run auctions. I'm particularly concerned about interactions with the multi-threaded bidding feature.
Good idea -- do you think it's sufficient for me to make the unittests subclass
BidderWorkletMultiThreadingTest instead BidderWorkletTest?
Yeah, that sounds like a good idea to me.
fresh_context_recycler = std::move(unused_context_recyclers_.back());
Abigail KatcoffHow do we ensure that the context is associated with the current thread?
unused_context_recyclers_ is a member of V8State which we always run with the same associated v8_runner.
Acknowledged
size_t thread_index = next_thread_index_;
Abigail KatcoffI don't understand how this works with multiple bidder threads. It looks like all of the contexts we create are tied to a single thread. That's not ideal, given we try to spread the load over all threads.
I increment thread_index in the for loop, so the load is spread over all the threads.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Commit-Queue | +1 |
I think we need a higher level integration test to ensure that we correctly run auctions. I'm particularly concerned about interactions with the multi-threaded bidding feature.
Russ HamiltonGood idea -- do you think it's sufficient for me to make the unittests subclass
BidderWorkletMultiThreadingTest instead BidderWorkletTest?
Yeah, that sounds like a good idea to me.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
@dcheng PTAL at blink/features. Thanks!
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Thanks!
<histogram name="Ads.InterestGroup.Auction.NumPremadeContextsScheduled"
Is this supposed to be `PremadeContextsScheduledPerThread`? Could you update the description as well, perhaps just 'Recorded when the context preparation tasks are posted in each bidder thread' (if that's correct)?
The number of contexts scheduled to be prepared before bids tasks are ready.
s/bids/bid/?
```suggestion
The number of contexts scheduled to be prepared before bid tasks are ready.
```
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
<histogram name="Ads.InterestGroup.Auction.NumPremadeContextsScheduled"
Is this supposed to be `PremadeContextsScheduledPerThread`? Could you update the description as well, perhaps just 'Recorded when the context preparation tasks are posted in each bidder thread' (if that's correct)?
Yes! Thanks, I forgot to update this when I made the name change.
The number of contexts scheduled to be prepared before bids tasks are ready.
s/bids/bid/?
```suggestion
The number of contexts scheduled to be prepared before bid tasks are ready.
```
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Thanks!
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |
Protected Audience: prepare contexts during trusted signals download
In the time between downloading bidding scripts and bidding signals,
prepare some contexts for later use by making the contexts,
running the top level script, and adding bindings. The worklet is
relatively idle during this time, and doing some preparation in
advance can improve the overall latency.
This can be further improved in a follow-up CL to make the contexts
before downloading the scripts, and running the top-level scripts
once we have them.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. | Gerrit |