- Mais recentes
- Mais votos
- Mais comentários
Hey Jim! I understand where you are coming from with this and that would be why I lean towards recommending Savings Plans at 80% coverage based on current usage. Once an end user understands their future use cases they can then apply another layer of an SP to move closer to 100%. If you still want more information I would suggest reaching out to an Optics Specialist or account concierge.
It's correct - the engine may in fact recommend RIs or SPs purchase that will get you to less than 100% utilization overall. RI/SP Utilization isn't a metric you should be going for, when it comes to business KPIs, and when it comes to deciding how much to commit. The actual realized savings is a much better indicator.
I can't confirm if we have this anywhere in the documentation, but I can certainly confirm that this is how recommendations engine works, after helping customers understand their commitment recommendations for many years. 100% utilization DOES NOT mean maximum savings. It all depends where's the break even point for your specific usage patterns.
How recommendations engine works? Think about it this way - it makes incremental assumptions... for example, first it checks, how much you'd be savings if you reserved $1 commitment... then how much you'd be savings if you reserved $2. It will reach certain point when it will make no sense to commit more (let's say... it might be at $10/hour) - in which case the engine will provide the most optimal recommendation (let's say, it could be $9.999/hour commitment); and it's true that the projected utilization may be below 100% let's say if you have spiky workloads, but if you would still benefit from committing to SPs.
Conteúdo relevante
- AWS OFICIALAtualizada há 8 meses
- AWS OFICIALAtualizada há 6 meses
- AWS OFICIALAtualizada há 8 meses
- AWS OFICIALAtualizada há 3 anos
Thank you. I am not trying to figure out how to advise a customer, but rather to understand how the engine itself works. Thank you for your advice.