How Elastic is the Oracle Cloud

By | July 16, 2019

Get 60% cost reduction and Super Speeds when needed, all on-the-fly!

One of the key characteristics of Cloud Computing is elasticity; resources that are available on-demand when needed and stopped when not needed, resources that can scale to the current demand. This elasticity is not only great to ensure well performing applications, but can also significantly help to reduce the cost of such solutions.

Let’s take an Example: You want to have an Analytics Environment to discover valuable data for your business. An analytics environment typically only needs to run when the user is actually working with it. This will clearly not be 24/7. The database behind the analytics environment might also only need to run during the use of analytics. So in some cases both can be powered off when not needed, resulting in significant cost saving.

Service Cost 24×7 per Month Cost 10×5 per Month Savings
Analytics Standard @ 2 OCPU $2,000 $896 $1,104 (55.2%)
Autonomous Data Warehouse @ 2 OPCU $2,500 $874 $1,626 (65.1%)
Total Monthly cost $4,500 $1,769 $2,731 (60,7%)

In case you are wondering why the savings on Autonomous DB is different then on Analytics cloud; Autonomous has zero CPU cost when not running, while the Analytics cloud charges 15% of CPU while not running.

Save Money, but get POWER when needed!

In the above example you see the savings these services can give you if you run them “smartly”, but sometimes you just want to go fast! These service support scaling so you will have that option. The above configuration/price is based on 2 OCPUs for each service but:

  • Autonomous DB can scale WITHOUT downtime from 1 to 128 OCPUS
  • AnalyticsCS can scale WITHOUT downtime between 2,4, 6 or 8 OCPUS

So if you need some extra juice, you can! You will only be paying extra for the duration (in hours) for the extra capacity.

Oracle Cloud Services Elasticity Overview

Service Suspend Suspend Cost Scale Up/Down OCPU Range Scale In/Out Comments
Compute VM Yes Storage Cost Non-automated, re-create new shape 1, 2, 4, 8, 16, 24 via Instance Pool Stopping of billing only for Standard shapes not based on Windows OS
Compute BM Yes Storage cost No 36,44,52,64 No Stopping of billing only for Standard shapes not based on Windows OS
Compute Instance Pool Yes Storage Cost No   Yes, 1 to many nodes  
Database VM Yes Storage Cost Non-automated, thru DB restore to new shape 1, 2, 4, 8, 16, 24 Yes, RAC 2 Nodes  
Database Bare Metal No   Yes 2 – 52 OCPU No DB license for OCPU is scalable. There is a fixed infrastucture cost for the BM server
Exadata CS Quarter X7 No   Yes 1 – 92 OCPU RAC 2 Nodes Fixed Infra cost. Minimum term is one month, there after per hour
Exadata CS Half X7 No   Yes 1 – 184 OCPU RAC 4 Nodes Fixed Infra cost. Minimum term is one month, there after per hour
Exadata CS Full X7 No   Yes 1 – 368 OCPU RAC 8 Nodes Fixed Infra cost. Minimum term is one month, there after per hour
Autonomous DB Yes Storage Cost Yes 1 – 128 OCPU Above 16 OCPU split on multiple RAC Nodes  
Analytics CS Yes 15% of OCPU hour rate Yes (2,4,6,8) or (10,12) No Shapes 1, 16, 24,236,52 do not provide scaling
Java CS Yes Storage Cost No   Yes, 1,2 or 4 Nodes  
Visual Builder CS Yes   No   No  
Big Data Cloud Yes Storage Cost No 2,4,8,16,24 Yes, 1 to 100 nodes  

Automation

While you can manually power on/off or scale these services, you likely want to build some automation around this. The Oracle Cloud provides a very rich API set so you can build this.

I have already an example “Super Scale” script that can automatically power on/off and scale Compute and Database Instances. I will also soon be adding support for the Analytics cloud and some other services in this script, so “To be continued…” 🙂

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.