5 documented OCI Compute Instances cost inefficiencies, each with how to detect it and how to fix it.
OCI Compute InstancesCER-0046
OCI Compute instances incur cost based on provisioned CPU and memory, even when the instance is lightly loaded. Instances that show consistently low usage across time, such as those used only for occasional tasks, test environments, or...
OCI Compute InstancesCER-0546
OCI compute instances keep billing for their OCPUs and memory for as long as they are running, whether or not they do any work. Instances are left running after a proof of concept ends, a test cycle finishes, a workload is migrated...
OCI Compute InstancesCER-0547
Some OCI virtual machines are idle most of the day and only need full CPU for short spikes, the workloads Oracle lists for burstable instances: development and test servers, CI/CD runners, monitoring systems, small microservices and static...
OCI Compute InstancesCER-0548
Older OCI tenancies often still run VMs on shapes that Oracle lists as previous generation, orderable only until 2020 to 2022 for most series, such as VM.Standard1, VM.Standard.B1, VM.Standard2, VM.Standard.E2, VM.Standard.E3 and...
OCI Compute InstancesCER-0549
OCI offers preemptible capacity that costs 50% less than on-demand capacity in all regions, in exchange for Oracle being able to reclaim the instance and terminate it at any time. Oracle positions it for fault-tolerant work that can...
