这是indexloc提供的服务,不要输入任何密码
Skip to content

Browser-side auction, resource management #79

@jonasz

Description

@jonasz

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:

  1. Do you envision a strict CPU usage limit per ad? Per advertiser? Per DSP?
  2. What happens if there's too many ads to evaluate? It seems the browser needs to be able to decide which ads to prioritize.
  3. It may be beneficial to allow DSPs to assign a "preliminary score" to ads, which could be used for such prioritization.
  4. 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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions