What is the problem and a valid solution?

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 IOPs 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?

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 IOPs 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.



Leave a Reply 7

Your email address will not be published. Required fields are marked *


Jake

Jake

E is irrelevant, the system doesn’t have any standard EBS volumes.
I would go with B.

balaji mariyappan

balaji mariyappan

I agree, it should B

webber

webber

B.
The EBS-Optimized throughput limits the total IOPS that can be utilized use an EBS-Optimized
instance that provides larger throughput.

DC

DC

B – you have to choose a larger instance of the same type (EBS-Optimized)

Gnart

Gnart

E is not correct; it presumed a standard EBS instance. The question launches a EC2 Instance EBS-Optimized and supports 500 Mbps, which could easily handled 32,000 x 16 KB throughput. The throughput was only 24,000 x 16 KB, so I was not sure why there would be a problem. Not sure if there is an answer, changing block size only increase or decrease the number of I/O, it does not effect throughput.