- 最新
- 投票最多
- 评论最多
Hi @REDACTEDUSER
GameLift Queue would prefer SPOT fleet as long as it is "viable". Viability is determined by the SPOT fleet's EC2 Instance Type, OS and Region. If those attribution combination is at risk for SPOT interruption, we deem it as unviable.
SPOT interruption, in layman's term, is EC2 reclaiming the SPOT fleet and reallocate it to ON_DEMAND. This typically happen when the EC2 instance type and OS have high usage in the region. 5th generation hosts (c5, m5, r5) that are larger than *.large typically have relatively low capacity but high usage, hence it's likely that all of your SPOT instances were unviable and caused GameLift queue to place into ON_DEMAND instead.
Here are some graphs illustrating the viability in the last 30 days in IAD for Linux:
REMOVEDUPLOAD REMOVEDUPLOAD
As you can see, *.large or 4th gen instance types are typically much more stable in viability. So, I'd recommend you to use c5.large or c4.xlarge to replace one of your x5.xlarge instance types.
You can find out about why your cheapest SPOT fleet wasn't placed by going to CloudWatch and search for "FirstChoiceNotViable" for your queue. https://docs.aws.amazon.com/gamelift/latest/developerguide/monitoring-cloudwatch.html.
相关内容
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前