1 Answer
- Newest
- Most votes
- Most comments
0
Hello,
A few items you can look into to investigate where that time is coming from:
- How long does it take for your game sessions to go active? You can test this by calling CreateGameSession on a fleet and checking how long it takes.
- Do you have enough capacity in your queue's fleets? Instances don't scale up instantly (assuming you're using a scaling policy), so if you're working with full or nearly full fleets, that will slow down your placement time.
- Is your queue's prioritization line up with your fleets scaling? Similar to above, but if your queue's priority/filter configurations make it so the first few choices are full fleets, the placements will need multiple attempts to find a destination. You may need to adjust how your queue filters/prioritizes, and/or you may need to focus on scaling for particular fleets that you want to take the most traffic.
If you after the above you need more explicit support for your resources, you can open a support case with AWS following this link: https://support.console.aws.amazon.com/support/home#/case/create
Regards,
answered 18 days ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago