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)


> that operation is often disk-io boundthe first time.. 12TB can cache a lot of logs.

At this size calculating power consumption is probably important, it\'s definitely no longer insignificant

> $802,538.64 for the 3-year term. I wonder how that compares to building your own on-premise host with that much RAMThis was discussed a couple days ago in a different thread [1], when 4TB was the EC2 limit.$400k for the current-gen (224 cores) or, as a sibling comment [2] notes, $250k for the previous CPU generation (which can use twice as many DIMMs of half the density and only 192 cores of that).> obviously, there\'s operational costs to consider as wellWe can estimate an upper bound on this, given that the current-gen system has N+2 5x1600W 96% efficient PSUs, so 5kW max. If you\'re paying a colo $.50/kWh, that\'s another $66k over 3 years worst case.Realistically, though, CPUs with a max TDP of 1640W, DIMMs (generously) 700W, leaves plenty of room for fans, SSDs and other overhead before getting to 3kW or $40k, and that\'s still assuming running full-bore the whole time.There are obviously also ancillary costs to AWS, such as data transfer and EBS.If you\'re already running your own hardware, it sure does look more attractive to pay $400k now and $40k over 3 years than to pay AWS $800k All Up Front (now). If not, perhaps it\'s more attractive to hand-wave away that $360k as saving the \"hassle\" of hiring someone who knows how to run equipment in a datacenter.