Cloud Mercato tested CPU performance using a range of encryption speed tests:
Cloud Mercato's tested the I/O performance of this instance using a 100GB General Purpose SSD. Below are the results:
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.
.png)


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.

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.