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)


While the chart above is a good start, there’s more than simply considering “Reserved vs. On Demand”. So let’s take a closer look at all the options…

Do .mental instances keep accruing compute charges when they are shutdown?

They are suited for scale-out workloads such as web servers, containerized microservices, caching fleets, distributed data stores, and development environments.

They are suited for scale-out workloads such as web servers, containerized microservices, caching fleets, distributed data stores, and development environments.

The a1 instance type was announced in late 2018 and can be a less expensive option than other EC2. They are suited for scale-out workloads such as web servers, [containerized microservices], caching fleets, distributed data stores, and development environments.

The a1 instance type was announced in late 2018 and can be a less expensive option than other EC2. They are suited for scale-out workloads such as web servers, [containerized microservices], caching fleets, distributed data stores, and development environments.

The a1 instance type was announced in late 2018 and can be a less expensive option than other EC2. They are suited for scale-out workloads such as web servers, [containerized microservices], caching fleets, distributed data stores, and development environments.

The t3 family is a burstable instance type. If you have an application that needs to run with some basic CPU and memory usage, you can choose t3. It also works well if you have an application that gets used sometimes but not others.

The a1 instance type was announced in late 2018 and can be a less expensive option than other EC2. They are suited for scale-out workloads such as web servers, containerized microservices, caching fleets, distributed data stores, and development environments.

Amazon EC2 is introducing instances that are powered by CPUs custom built by Amazon on the Arm architecture.

Thank you for clarifying the conclusion. We have a concrete reason to need nested VMs running on EC2. Hopefully AWS will continue to provide a1.metal for a long time as it's relatively reasonable price among all metal instances.

Thank you for answering this. If my understanding is correct, ARMv8.3 or above has a support of nested virtualization in architecture level while Intel requires optional CPU feature, VT-x. It sounds to me that the answer of a post below implies nested virtualization would be available once Graviton has ARMv8.3 or above architecture. These are why I had a hope of running VM on a non-metal Graviton instance.

Only bare metal[1,2] EC2 instances provide direct access to cpu of the underlying server and its' features like Intel VT-x required to run your own hypervisor.

EC2 instances are priced according to instance type, regardless of the number of CPUs enabled. Disabling vCPUs does not change the cost of the instance type.

Do .mental instances keep accruing compute charges when they are shutdown?