Learn how Palo Alto Networks is Transforming Platform Engineering with AI Agents. Register here

Attend a Live Product Tour to see Sedai in action.

Register now
More
Close
AWS

c6g.large

EC2 Instance

ARM-based compute-optimized instance with 2 vCPUs and 4 GiB memory. Good for compute-bound applications that can run on ARM architecture.

Coming Soon...

icon
Pricing of
c6g.large

N/A

On Demand

N/A

Spot

N/A

1 Yr Reserved

N/A

3 Yr Reserved

Pricing Model
Price (USD)
% Discount vs On Demand
sedai

Let us help you choose the right instance

Schedule a meeting
icon
Spot Pricing Details for
c6g.large

Here's the latest prices for this instance across this region:

Availability Zone Current Spot Price (USD)
Frequency of Interruptions: n/a

Frequency of interruption represents the rate at which Spot has reclaimed capacity during the trailing month. They are in ranges of < 5%, 5-10%, 10-15%, 15-20% and >20%.

Last Updated On: December 17, 2024
icon
Compute features of
c6g.large
FeatureSpecification
icon
Storage features of
c6g.large
FeatureSpecification
icon
Networking features of
c6g.large
FeatureSpecification
icon
Operating Systems Supported by
c6g.large
Operating SystemSupported
icon
Security features of
c6g.large
FeatureSupported
icon
General Information about
c6g.large
FeatureSpecification
icon
Benchmark Test Results for
c6g.large
CPU Encryption Speed Benchmarks

Cloud Mercato tested CPU performance using a range of encryption speed tests:

Encryption Algorithm Speed (1024 Block Size, 3 threads)
AES-128 CBC 386.8MB
AES-256 CBC 287.2MB
MD5 765.5MB
SHA256 2.8GB
SHA512 721.1MB
I/O Performance

Cloud Mercato's tested the I/O performance of this instance using a 100GB General Purpose SSD. Below are the results:

Read Write
Max 3099 3099
Average 3097 3097
Deviation 2.66 3.09
Min 3091 3089

I/O rate testing is conducted with local and block storages attached to the instance. Cloud Mercato uses the well-known open-source tool FIO. To express IOPS the following parametersare used: 4K block, random access, no filesystem (except for write access with root volume and avoidance of cache and buffer.

icon
Community Insights for
c6g.large
AI-summarized insights
filter icon
Filter by:
All

Amazon EC2 C6g instances are powered by Arm-based AWS Graviton2 processors. They deliver up to 40% better price performance over current generation C5 instances for compute-intensive applications.

28-10-2024
benchmarking, graviton, cost_savings

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

Is there any other documentation that compares performance between different generations (c5/c6/c7) and processor types (c6i vs c6g, for example)? The on-demand pricing per hour for a c6i.large (or a c5.large) instance is 25% more than for a c6g.large, which is not insignificant. And why does documentation for the AWS FGT 7.0 recommend c6i or c6g, whereas 7.2 and 7.4 recommend only c5?

Amazon EC2 - c6g.large performance is very stable over long periods of time

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

Overall we are happy with performance, compared to old stack we are at around 10% of the cost and I think our savings was more than 2x compared to x86 after locking in some rates. R6gd.metal (16x) vs R5d.metal (24x)

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

Is there any other documentation that compares performance between different generations (c5/c6/c7) and processor types (c6i vs c6g, for example)? The on-demand pricing per hour for a c6i.large (or a c5.large) instance is 25% more than for a c6g.large, which is not insignificant. And why does documentation for the AWS FGT 7.0 recommend c6i or c6g, whereas 7.2 and 7.4 recommend only c5?

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

Amazon EC2 - c6g.large performance is very stable over long periods of time

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

The other difference is memory, your t2.micro instance has 1GB memory whereas the c6g.medium has 2GB of memory allocated, which also increases the price. Then there is the CPU architecture which is ARM, which won't be able to run x86 compiled applications natively and some applications will need to be recompiled specifically to run successfully.

Load More
Similar Instances to
c6g.large

Consider these:

Feedback

We value your input! If you have any feedback or suggestions about this t4g.nano instance information page, please let us know.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.