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)


The M7 instances have a slight speed advantage even though the overall specification is the same with 2vCPU and 8GB of memory.

But how does this explain that t3a.large and m5a.large show different cpu usage during baseline (not burst)? It is the same hardware and we run the same applications.

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk.

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk. It’s not hard to see why almost half of EC2 workloads [are on “m” instances].

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk. It’s not hard to see why almost half of EC2 workloads [are on “m” instances].

The m5 instance type is similar, but for more consistent workloads. It has a nice balance of CPU, memory, and disk. It’s not hard to see why almost half of EC2 workloads [are on “m” instances].