Data egress is one of the trickiest factors when it comes to calculating cloud computing. Inbound traffic is usually inexpensive or free, but outbound traffic? That’s a different story. Thankfully, Oracle has released a new Cloud Workload Estimator to make the estimating process a little easier.
How the Oracle Cloud Workload Estimator works
Oracle’s new estimator categorizes different types of workloads to calculate how much each business might spend on computing, storage, data transmission, and more. The bandwidth intensive category focuses on workloads with large volumes of egress traffic. Enter the approximate outbound traffic per month, measured in terabytes, and see what the cost of Oracle Cloud is in comparison to Amazon Web Services (AWS).
The calculator offers additional fine-tuning features for more accuracy—compute-light, compute-heavy and balanced profile.
The Cloud Workload Estimator also calculates based on block storage consumption in the I/O intensive category, or based on the number of instances in the general purpose category. The general purpose covers workloads with a balance of memory, compute, and networking. Finally, the estimator has a build-your-own option that’s fully customizable for accurate cost calculations.
How does OCI compare to AWS by cost?
Oracle Cloud tends to be more affordable across the board, but the volume of savings depends on the type of workload. Businesses with significant data egress can expect to save quite a bit because of the way Oracle’s pricing is structured. With AWS, the markup for outbound traffic starts at 1 TB. With OCI, it doesn’t start until 10 TB.
To put that in perspective, a balanced profile workload with 20 TB of data egress per month would save approximately 90% per month with OCI, dropping from $2,008 per month to just $198. Jump to 1,000 TB per month and the savings comes out to over $21,000 per month. The Oracle Cloud Workload Estimator takes the guesswork out of data egress expenses and makes it easy to pinpoint the cost of cloud computing.No tags for this post.