googleforgames
Document Allocation batching
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
'This issue is marked as Stale due to inactivity for more than 30 days. To avoid being marked as 'stale' please add 'awaiting-maintainer' label or add a comment. Thank you for your contributions '
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @markmandel, I have some queries about this issue — the batch allocation value (500ms) keeps changing, but it’s not updated anywhere in the documentation. So I added this link to the document. Is that correct?
the batch allocation value (500ms) keeps changing,
Sorry - not sure what you mean. How does it keep changing? Can you say more?
but it’s not updated anywhere in the documentation. So I added this link to the document. Is that correct?
You added the link where?
Sorry - not sure what you mean. How does it keep changing? Can you say more?
Sorry about this. My question is: the batchAllocationWaitTime value can be changeable, but it’s not documented anywhere — needs to be added
Ah - see original post, this bit:
Additional context