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)


It turns out the RIs were in the Availability Zone, not in the Region, so I was not getting the benefit of size-flexibility. The thing that eventually tipped me off was I bought 8 \"nano\" RIs, and had one nano instance running. My Utilization Report showed 12.5%, so I figured the RIs weren\'t being applied to my larger instances. I changed the RIs to be in the Region, and my Utilization Report immediately improved.

I had an expiring RI for a t4g.large instance, and Amazon recommended I buy (8) t4g.nano RIs. I have since replaced the t4g.large instance with a t4g.medium and t4g.nano instance, thinking I was reducing my overall usage. But now the Cost Explorer is showing my costs have risen over 100%, the RI Utilization Report shows a steep decline, which matches the decline in the RI Coverage Report. Worse, the recommendation engine is now recommending I buy (10) more t4g.nano instances. All my instances are running in the same Availability Zone (us-east-1c). They\'re all t4g instances. They all run Ubuntu. They all have default tenancy (shared). My usage has been steady for the last year. The only change I can see is the RI conversion. I\'m not getting the expected benefit of the nano RIs. What is going on? How do I get these new RIs to cover my usage?

Cost Explorer is your best option to review and understand the usage and coverage in order to review your recommendations which would help in a big way! Another thing to note that there is a normalization factor that you need to consider which would match the recommendations. For instance size nano= 0.25 (normalization factor), micro=0.5, small=1, medium=2 and large=4, similarly the rest of them.

It turns out the RIs were in the Availability Zone, not in the Region, so I was not getting the benefit of size-flexibility. The thing that eventually tipped me off was I bought 8 \"nano\" RIs, and had one nano instance running. My Utilization Report showed 12.5%, so I figured the RIs weren\'t being applied to my larger instances. I changed the RIs to be in the Region, and my Utilization Report immediately improved.

I had an expiring RI for a t4g.large instance, and Amazon recommended I buy (8) t4g.nano RIs. I have since replaced the t4g.large instance with a t4g.medium and t4g.nano instance, thinking I was reducing my overall usage. But now the Cost Explorer is showing my costs have risen over 100%, the RI Utilization Report shows a steep decline, which matches the decline in the RI Coverage Report. Worse, the recommendation engine is now recommending I buy (10) more t4g.nano instances. All my instances are running in the same Availability Zone (us-east-1c). They\'re all t4g instances. They all run Ubuntu. They all have default tenancy (shared). My usage has been steady for the last year. The only change I can see is the RI conversion. I\'m not getting the expected benefit of the nano RIs. What is going on? How do I get these new RIs to cover my usage?