哪种RDS实例类型具有更好的IO:特大数据库实例或高内存特大实例 [英] Which RDS instance type has better IO: Extra Large DB Instance or High-Memory Extra Large Instance

问题描述

我在使用MySQL 5.5.12的Amazon RDS上出现了IO性能问题.有两种实例类型相似且价格接近:

I am getting IO performance concerns with Amazon RDS using mysql 5.5.12. There are 2 instance types that are similar and close in price:

超大型数据库实例:15 GB内存，8个ECU(4个虚拟内核，每个虚拟内核有2个ECU)，64位平台，高I/O容量(仅MySQL DB引擎)(每小时$ 0.88)

Extra Large DB Instance: 15 GB of memory, 8 ECUs (4 virtual cores with 2 ECUs each), 64-bit platform, High I/O Capacity (MySQL DB Engine Only) ($0.88 per hour)

高内存超大型实例17.1 GB内存，6.5 ECU(2个虚拟内核，每个虚拟内核分别具有3.25 ECU)，64位平台，高I/O容量(每小时$ 0.65)

High-Memory Extra Large Instance 17.1 GB memory, 6.5 ECU (2 virtual cores with 3.25 ECUs each), 64-bit platform, High I/O Capacity ($0.65 per hour)

有人知道超大型数据库的IO速度是否比高内存超大型实例的快?

Does anyone know if the Extra Large DB has faster IO than High-Memory Extra Large Instance?

推荐答案

m1.xlarge实例(您提到的64位/15GB)全部拥有一个NIC，因此具有最佳的网络(扩展名为EBS)表现.通过条带化，您可以承受1500磁盘iops，而与标准100 iops相反.

m1.xlarge instances (the 64-bit/15GB you mention) get a NIC all to themselves and therefore have the best network (and by extension, EBS) performance. With striping you can sustain 1500 disk iops, as oppossed to the standard 100 iops.

在RDS中使用时，通过将存储大小设置为至少300GB，您将看到最高的iops，这将触发后端条带化.

When used in RDS, you will see highest iops by setting your storage size to at least 300GB, which triggers back-end striping.

如果您需要更多的RAM或CPU，则只有c1.xlarge和m2.4xlarge实例类型本身具有完整的NIC-它们还需要300GB的存储分配才能使用它.

If you need more RAM or CPU, only the c1.xlarge and m2.4xlarge instance types have the full NIC to themselves- they would also required 300GB storage allocation to take advantage of it.

这篇关于哪种RDS实例类型具有更好的IO:特大数据库实例或高内存特大实例的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！