Skip to content

Document Allocation batching #3635

@markmandel

Description

@markmandel

Is your feature request related to a problem? Please describe.

By default Agones batches allocations for better throughput by 500ms at a time. In some scenarios, that amount of wait time is overkill. But what happens in allocation and the tradeoffs for changing this value is not documented anywhere, so it's hard to judge.

Describe the solution you'd like

The following documentation added:

  • How Agones Allocation batching works
  • How to configure it (already exists in Helm config, but good to reiterate)
  • The tradeoffs there (may impact CPU and potentially throughput).

I was thinking here:
https://agones.dev/site/docs/reference/gameserverallocation/

Maybe with an update to the formatting of how the cache performs.

Describe alternatives you've considered

Leave the documentation alone - but the issue has come up a few times in offline discussions, so its worth documenting.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions