-
Notifications
You must be signed in to change notification settings - Fork 269
Closed
Description
Hi,
During browser-side auction execution the computational resources will be limited, and so there will be a need for a resource management mechanism. The main bottleneck will likely be CPU time usage, but other resources should also be managed.
Some questions and thoughts that come to mind:
- Do you envision a strict CPU usage limit per ad? Per advertiser? Per DSP?
- What happens if there's too many ads to evaluate? It seems the browser needs to be able to decide which ads to prioritize.
- It may be beneficial to allow DSPs to assign a "preliminary score" to ads, which could be used for such prioritization.
- Prioritization of ads coming from different DSPs is more tricky. The prioritization should be "fair", in some sense - for instance, an advertiser/DSP that rarely wins should not be allowed to consume the majority of resources.
Perhaps we could think of mechanisms that gamify the prioritization process between DSPs so as to optimize the final bid value (or some other metric)?
It would be great to hear your thoughts on that, even if you don't have a specific solution in mind yet.
Best regards,
Jonasz
Metadata
Metadata
Assignees
Labels
No labels