enum AllocationStrategy
| Language | Type name |
|---|---|
 .NET | Amazon.CDK.AWS.Batch.AllocationStrategy |
 Go | github.com/aws/aws-cdk-go/awscdk/v2/awsbatch#AllocationStrategy |
 Java | software.amazon.awscdk.services.batch.AllocationStrategy |
 Python | aws_cdk.aws_batch.AllocationStrategy |
 TypeScript (source) | aws-cdk-lib » aws_batch » AllocationStrategy |
Determines how this compute environment chooses instances to spawn.
Example
declare const vpc: ec2.IVpc;
const computeEnv = new batch.ManagedEc2EcsComputeEnvironment(this, 'myEc2ComputeEnv', {
vpc,
allocationStrategy: batch.AllocationStrategy.BEST_FIT,
});
Members
| Name | Description |
|---|---|
| BEST_FIT | Batch chooses the lowest-cost instance type that fits all the jobs in the queue. |
| BEST_FIT_PROGRESSIVE | This is the default Allocation Strategy if spot is false or unspecified. |
| SPOT_CAPACITY_OPTIMIZED | If your workflow tolerates interruptions, you should enable spot on your ComputeEnvironment and use SPOT_CAPACITY_OPTIMIZED (this is the default if spot is enabled). |
| SPOT_PRICE_CAPACITY_OPTIMIZED | The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price. |
BEST_FIT
Batch chooses the lowest-cost instance type that fits all the jobs in the queue.
If instances of that type are not available, the queue will not choose a new type;
instead, it will wait for the instance to become available.
This can stall your Queue, with your compute environment only using part of its max capacity
(or none at all) until the BEST_FIT instance becomes available.
This allocation strategy keeps costs lower but can limit scaling.
BEST_FIT isn't supported when updating compute environments
BEST_FIT_PROGRESSIVE
This is the default Allocation Strategy if spot is false or unspecified.
This strategy will examine the Jobs in the queue and choose whichever instance type meets the requirements
of the jobs in the queue and with the lowest cost per vCPU, just as BEST_FIT.
However, if not all of the capacity can be filled with this instance type,
it will choose a new next-best instance type to run any jobs that couldn’t fit into the BEST_FIT capacity.
To make the most use of this allocation strategy,
it is recommended to use as many instance classes as is feasible for your workload.
SPOT_CAPACITY_OPTIMIZED
If your workflow tolerates interruptions, you should enable spot on your ComputeEnvironment and use SPOT_CAPACITY_OPTIMIZED (this is the default if spot is enabled).
This will tell Batch to choose the instance types from the ones you’ve specified that have the most spot capacity available to minimize the chance of interruption. To get the most benefit from your spot instances, you should allow Batch to choose from as many different instance types as possible.
SPOT_PRICE_CAPACITY_OPTIMIZED
The price and capacity optimized allocation strategy looks at both price and capacity to select the Spot Instance pools that are the least likely to be interrupted and have the lowest possible price.
The Batch team recommends this over SPOT_CAPACITY_OPTIMIZED in most instances.