Windows Azure Cost Saving Tips (Part 1) : Compute Costs

Posted on Posted in Uncategorized

Well, we have all heard about benefits of cloud computing. However, for many novice readers and a ton of traditional enterprise shops who are yet to get their cloud computing feet wet, have no idea on how to translate those to tangible benefits.

(Recap here for new reader’s benefits

  • Utility computing – Pay per use
  • Virtualized computing resources that are remote and abstract.
  • Elasticity – On demand Provisioning and De-provisioning
  • Scalability in minutes
  • Allows IT to shift focus from managing infrastructure to managing business.)

We plan to start a series of articles, with a tip or two in every post to help you get on top of managing costs. Sure, take these you’re your CTO and get ready for a big bonus yourself J

Tip 1: Compute Costs are the highest order bit in managing costs

While there are lot of things we will recommend you to look at, we believe that the most important one is your Billing statement.

After analyzing many of our clients billing statements, we find the following general gotchas

(Of course, this is a generic analysis. We advise you to watch out on your specific usage across Compute, Storage and Bandwidth resources)

  1. Forgetting to Shut down Virtual machines instances that are not in use

    Did you know that Windows Azure now supports ‘No charge for stopped VM’s‘. Small and Medium businesses do not really have a great application lifecycle management practices in place. Understood that you are in a hurry to develop and get your application/service ‘to the cloud’. However, watch out for all your compute costs across development, test, staging and production subscriptions.

    Of course, we wish that Windows Azure makes this an inclusive feature and applies to Hosted Services/Cloud services. But guess what, they might have this in the works.

  2. Choosing a wrong instance size

    Do you really need ‘big’ instances? Instead of a big-one, could you not use multiple smalls? Here’s why…

    Apart from the fact that you are getting beefier hardware (progressively more CPU and RAM) as you go up the instance size chain, you should also be aware that the costs rise geometrically (~constant ratio of 2)

    So choose your instance size wisely.

    Of course, we have heard many arguments that design for scaling out takes effort and needs lots of attention to detail. However, you will have to go through that phase if you need the much required SLA advantages

    Here’s some data gleaned from Windows Azure calculator (as of 7/5/2013)

     

instance sizecost for 2 instances/ monthCompare Costs to XSCPU (GHz)RAM (GB)cost ratio
XS29.76110.768
S133.924.51.61.752.278646
M267.8493.23.52
L535.68186.472
XL1071.363612.8142
A61517.76516.4282
A73035.5210212.8562

 

Apply these guidance’s today and we will take this journey next week with more cost saving tip around compute resources.

Risparmiare denaro. Ciao

(Bye and Save Money)

Leave a Reply

Your email address will not be published. Required fields are marked *