dmorgan-blizz

Unfortunately, https://github.com/googleforgames/agones/pull/4159 did not solve our allocation problems ;( we see very similar behavior on 1.49 as we did on 1.44, where more gameservers are spun up than needed. For...

I hadn't seen https://github.com/googleforgames/agones/issues/4190 that sounds great! I'm fine with waiting for that :)

Interesting...and `one allocation client` means one execution of `tmp/allocate.sh` https://github.com/googleforgames/agones/pull/4059/files#diff-2863a956029e7b0d4dbada6deccdef2e148548b5c545df26950c05e93ee347f1 which is making serial requests? And if you introduce another execution (thus, now concurrent requests), the issue reproduces? Many concurrent...

My results mostly match up, though there were a few oddities. Overall, it seems that yes, when only allowing our server to make one AllocationRequest at a time, the packing...

> > One thing to note, I don't think this can ever be perfect, but I think we can make it better. Each cache in the allocator is eventually consistent,...

Is there way to make this request more official/see that it makes its way into an upcoming release? This would _greatly_ improve our resource/node utilization if this packing was more...