In the first blog in this series, we looked at why it’s so important to look at an application’s workload patterns when sizing for any public cloud, including AWS, Microsoft Azure, Google Cloud Platform, and others.
In this post, we’ll look at another common pitfall that we call the cloud instance “bump-up loop.”Here’s how it works. You use a reporting tool that says your application workload is running at nearly 100% utilization for 3 hours overnight (see figure below). Densify
The tool is designed to interpret high utilization as bad, and concludes that the workload is under-provisioned.
So, it recommends bumping up the CPU resources, and in doing so increases your costs.

But a funny thing happens: despite the change, the next day the workload still runs at 100%, just for a shorter period of time. Once again, tool says to throw more resources at it.

The next day you see the workload still runs at 100%, but again for a shorter period of time.

And so on. Now you’re stuck in the endless capacity bump-up loop.To read this article in full or to leave a comment, please click here

Leave a Reply