Here you are.
And welcome back.
Now, in today's video, we'll be discussing about the allocation strategy for the sport instances.
Now, before we go, I and understand that it's important for us to have a misunderstanding about the
sport, instant sport.
So a sport instance full is basically a set of unused two instances with the same instance type and
availability zone within the region.
For example, let's assume that you have a sport, for instance, pool, for instance, type of environment.
And from you, you go ahead and launch multiple sets of instances to go ahead and perform your operation.
Now, one of the challenges with this type of approach is that in case if this pool gets used up, so
basically maybe because of bidding or maybe because someone has created many of the OnDemand instances,
then essentially all of the two instances that you have created from the sport, for instance, pool
will also be terminated.
And hence, depending upon the use case of your two instance and the criticality, it is important to
go ahead and select right allocation strategy.
Now, there are three primary types of allocation strategies that are available.
One is based on the lowest price, second is diversified, and third is capacity optimized.
So the lowest priced strategy is pretty straightforward.
The sport instances come from the sport capacity pool with the lowest price and this is one of the default
strategy.
Diversified is where the sport instances are distributed across all of the capacity pool.
So you do not really have sport instances just based on one of the capacity pools.
There are multiple capacity pools based on different instance shapes and then you diversified it.
And the third one is the capacity optimized.
Now, in this type of approach, the sport instances are basically launched from the pools that are
mostly available, and this happens by analyzing the capacity matrix.
So your pricing is not really looked into as a priority factor, but the overall availability based
on the capacity matrix is being looked upon.
Now, let's look into when you should use each one of them.
The first one is the lowest price option.
So in case if your fleet is small or runs for a short amount of time, then the probability of your
instance is being interrupted is low and hence you can go ahead and choose the lowest price allocation
strategy.
Now, do know that specifically, if you're using it as part of the auto scaling, the price constantly
changes of the sport instances.
And this can lead to the termination of the existing EU instances, which would be replaced by a new
cheaper ones, and hence it can disrupt your service at a higher rate.
So you have to make sure that you choose the right allocation strategy based on your current set of
requirements.
The second one is diversified.
So in case if your fleet is large, this is very important.
In case of your fleet is large or runs for a long period of time, then you can improve the reliability
of your fleet by distributing the sport instances across multiple pools.
So, for example, let's say you have two fleet which consist of penpals and a target capacity of 400
instances.
So from each of the pool.
So from each one of the bullets, a pool of morphologic, there will be 10 instances, maybe from a
different instance type, there'll be 10 instances and so on.
So now what will happen is that if the spot price for one of the pool exceeds your maximum price that
you have it, then only 10 percent of the fleet is affected.
So if your maximum price for a large is lower, then what is the current price of sport instant's then
be your end instances that are part of the sport.
Instant's pool of Vitalogy will be terminated, but at that 90 instances which are from a different
instance, pool will continue to run.
So that is what diversified is all about.
And the third one is the capacity to optimize.
So if your fleet runs a workload that may have a higher cost of interruption associated with restarting
work, then you should basically make use of capacity optimized.
Now, one of the important thing to note here is that this strategy does not look at the prices of the
instance type in each pool.
However, it primarily looks into the optimal capacity volume and then it chooses to run those incidents
based on that.
So at a high level, or you do note that although the overall early cost of a capacity optimized strategy
might be slightly higher, the possibility of having fewer interruptions can lower the overall cost
of your workload.
Now, generally, the easy two instances that are associated with the capacity optimized instance primarily
deals with various workloads like machine learning, immediately adding big data computing.
And those kind of workloads are primarily they use capacity optimized because the.
There is a higher cost of interruption there, so that's the very high level overview about the allocation
strategies for spot instances.