You have launched an EC2 instance with four (4) 500 GB EBS Provisioned IOPS volumes attached The EC2
Instance Is EBS-Optimized and supports 500 Mbps throughput between EC2 and EBS The two EBS volumes are
configured as a single RAID o device, and each Provisioned IOPS volume is provisioned with 4.000 IOPS (4 000
16KB reads or writes) for a total of 16.000 random IOPS on the instance The EC2 Instance initially delivers the
expected 16 000 IOPS random read and write performance Sometime later in order to increase the total
random I/O performance of the instance, you add an additional two 500 GB EBS Provisioned IOPS volumes to
the RAID Each volume Is provisioned to 4.000 lOPs like the original four for a total of 24.000 IOPS on the EC2
instance Monitoring shows that the EC2 instance CPU utilization increased from 50% to 70%. but the total
random IOPS measured at the instance level does not increase at all.
What is the problem and a valid solution?
A.
Larger storage volumes support higher Provisioned IOPS rates: increase the provisioned volume storage of
each of the 6 EBS volumes to 1TB.
B.
The EBS-Optimized throughput limits the total IOPS that can be utilized use an EBS-Optimized instance that
provides larger throughput.
C.
Small block sizes cause performance degradation, limiting the I’O throughput, configure the instance device
driver and file system to use 64KB blocks to increase throughput.
D.
RAID 0 only scales linearly to about 4 devices, use RAID 0 with 4 EBS Provisioned IOPS volumes but increase
each Provisioned IOPS EBS volume to 6.000 IOPS.
E.
The standard EBS instance root volume limits the total IOPS rate, change the instant root volume to also be
a 500GB 4.000 Provisioned IOPS volume.
b
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-ec2-config.html
E?
Here at issue, IOPS rather than throughput?
I think you should increase not throughput but IOPS.
The answer is B b/c EC2 Instance types have limit on max throughput and would 8xlarge or higher instance types to provide 24000 IOPS.
answer is b
EC2 Instance types have limit on max throughput and would 8xlarge or higher instance types to provide 24000 IOPS
B
In the question, Nowhere is mentioned what instance type he is using so B can not be right answer. Right answer is E.
B is the right answer.
Here is why: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-ec2-config.html
Launching an instance that is EBS-optimized provides you with a dedicated connection between your EC2 instance and your EBS volume. However, it is still possible to provision EBS volumes that exceed the available bandwidth for certain instance types, especially when multiple volumes are striped in a RAID configuration. Be sure to choose an EBS-optimized instance that provides more dedicated EBS throughput than your application needs; otherwise, the Amazon EBS to Amazon EC2 connection will become a performance bottleneck.
@vladam: Thanks, just want to note the keyword is “…Be sure to choose an EBS-optimized instance that provides more dedicated EBS..”
The Question says “The EC2 Instance Is EBS-Optimized and supports 500 Mbps throughput between EC2 and EBS”, which means it is an 8xlarge or higher instance already so I don’t see how B can be the right answer
B can. Please refer to the link
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSOptimized.html
I choose B.
500 Mbps is the spec for c4.large. Its maximum IOPS is 4,000.
C4.8xlarge’s expected throughput is 500 MB/s (equivalent to 4,000 Mbps). Its maximum IOPS is 32000.
B is wrong
E. The standard EBS instance root volume limits the total IOPS rate, change the instant root volume to also be a 500GB 4.000 Provisioned IOPS volume.
Answer is E
i think B
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-ec2-config.html
Instance types with 10 Gigabit network connectivity support up to 800 MB/s of throughput and 48,000 16K IOPS for unencrypted Amazon EBS volumes and up to 25,000 16K IOPS for encrypted Amazon EBS volumes. Because the maximum io1 value for EBS volumes is 20,000 for io1 volumes and 10,000 for gp2 volumes, you can use several EBS volumes simultaneously to reach the level of I/O performance available to these instance types.
So increase the EC2 network connectivity higher than 500MB/s would help
B
See: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-ec2-config.html
Choose an EC2 Instance with Enough Bandwidt: “Launching an instance that is EBS-optimized provides you with a dedicated connection between your EC2 instance and your EBS volume. However, it is still possible to provision EBS volumes that exceed the available bandwidth for certain instance types, especially when multiple volumes are striped in a RAID configuration”