Why it matters
Instances often stay on the shape they were first created with. Changing the shape at the same size keeps the workload’s capacity and lowers the hourly price.How nOps finds it
nOps reads the last 7 complete days of OCI Compute billing for instances on the Standard X9 OCPU and memory meters, billed on at least 5 of those days. Using Oracle’s public list prices (X9: $0.04 per OCPU-hour and $0.0015 per GB-hour of memory; E5 and E6: $0.03 and $0.002), it applies the OCPU price difference to the instance’s OCPU cost and the memory price difference to its memory cost, then scales to a month. Because memory costs more on E5 and E6, instances with a lot of memory per OCPU save less. The saving must be at least $5 a month, and tenancies with 90% or more of compute spend covered by credits are left out.Before you start
Confirm the workload and its operating system image run on AMD processors.How to implement
- Check that the instance’s image and software support AMD (most Linux and Windows images do).
- In the OCI Console, open the instance and choose Edit → Change shape, then pick VM.Standard.E5.Flex or VM.Standard.E6.Flex with the same OCPUs and memory (or use
oci compute instance update --instance-id INSTANCE_OCID --shape VM.Standard.E5.Flex --shape-configwith the OCPU and memory values). - Confirm the change; the instance restarts.
- Update Terraform or Resource Manager stacks so the shape is not changed back.
Risks and considerations
- Changing the shape restarts the instance, so plan a maintenance window.
- Software licensed per processor type, or tuned for Intel, may need checking.
- To roll back, change the shape back to X9.
FAQs
Why is the saving lower for some instances?
Why is the saving lower for some instances?
E5 and E6 list OCPUs lower than X9 but memory slightly higher, so an instance with a lot of memory per OCPU saves less.