Sedai raises $20 million for the first self-driving cloud!
Read Press Release

Attend a Live Product Tour to see Sedai in action.

Register now
More
Close
AWS

hpc7g.16xlarge

EC2 Instance

ARM-based high performance computing instance with 64 vCPUs, 128 GiB memory, and up to 800 Gbps networking. Highest capacity in Hpc7g family for demanding HPC applications on ARM.

Coming Soon...

icon
Pricing of
hpc7g.16xlarge

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
hpc7g.16xlarge

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
hpc7g.16xlarge
FeatureSpecification
icon
Storage features of
hpc7g.16xlarge
FeatureSpecification
icon
Networking features of
hpc7g.16xlarge
FeatureSpecification
icon
Operating Systems Supported by
hpc7g.16xlarge
Operating SystemSupported
icon
Security features of
hpc7g.16xlarge
FeatureSupported
icon
General Information about
hpc7g.16xlarge
FeatureSpecification
icon
Benchmark Test Results for
hpc7g.16xlarge
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 N/A
AES-256 CBC N/A
MD5 N/A
SHA256 N/A
SHA512 N/A
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 N/A N/A
Average N/A N/A
Deviation N/A N/A
Min N/A N/A

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
hpc7g.16xlarge
AI-summarized insights
filter icon
Filter by:
All

Maybe this is new as there's a 'Running On-Demand HPC instances' quota in the 'Service Quotas' tab. I won't know if this is the issue until they approve my request. NOTE: I've launched hundreds of instances with the AMI so, if there were some incompatibility issues, it'd be at the hpcg7g end.

18-03-2025

I usually launch directly from the console. The CLI is outputting: aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=hpc7g.16xlarge --region us-east-1 { "InstanceTypeOfferings": [ { "InstanceType": "hpc7g.16xlarge", "LocationType": "availability-zone", "Location": "us-east-1c" } ] } I tried specifying choosing the available subnet for us-east-1c (instead of letting the console choose whichever it prefers as I usually do), but the launching initiation failed. I wish that re:Post allowed me to post screenshots but a copy of the logs reads: Instance launch failed Value (hpc7g.16xlarge) for parameter instanceType is invalid. 'hpc7g.16xlarge' is an unsupported instance type Launch log Initializing requests Succeeded Creating security groups Succeeded Creating security group rules Succeeded Launch initiation Failed Regarding the AMI, I built my own, which has worked in pretty much every Gv2 or Gv3 instance (e.g. r6g, r7g, t4 ) and it worked even with c7gn yesterday and earlier today.

Generally, you might receive such error in one of the following two issues: 1. The specified instance type isn't supported in the requested Availability Zone. 2. The Amazon Machine Image (AMI) that's used to launch the instance doesn't support the selected instance type.

Check Service Quotas in the Console and ensure that you have a limit greater than 0 for the instance type. Make sure that the Architecture that you are specifying matches the instance. hpc7g.16xlarge The "g" in the instance type indicates it is a Graviton (64bit ARM) instance and not x86_64. Try launching with a default Amazon Linux AMI just to ensure that your custom image is not the issue.

Maybe this is new as there's a 'Running On-Demand HPC instances' quota in the 'Service Quotas' tab. I won't know if this is the issue until they approve my request. NOTE: I've launched hundreds of instances with the AMI so, if there were some incompatibility issues, it'd be at the hpcg7g end.

Just keep in mind that AMIs either support x86_64 or ARM, not both with the same AMI.

I'm trying to test Gv3(E). Instances c7gn are launching but when I try to launch an hpc7g.16xlarge instance, it keeps telling me that it's an unsupported instance type.

Load More
Similar Instances to
hpc7g.16xlarge

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.