July 30, 2015 at 8:28 am
I'm green on the storage system, so bear with me. I have a production SQL Server that has a lot of writes and reads. If I want to accommodate 400 Mb/Sec peak IO we currently have, how should I provision AWS EBS volumes? How much provisioned IOPS I should get?
I don't have much time to do a benchmarking. If this is not enough info to determine the sizing, what's the simplest procedure to get a close estimate on IOPS?
Thanks.
July 30, 2015 at 2:18 pm
Michelle-138172 (7/30/2015)
I'm green on the storage system, so bear with me. I have a production SQL Server that has a lot of writes and reads. If I want to accommodate 400 Mb/Sec peak IO we currently have, how should I provision AWS EBS volumes? How much provisioned IOPS I should get?I don't have much time to do a benchmarking. If this is not enough info to determine the sizing, what's the simplest procedure to get a close estimate on IOPS?
Thanks.
For IOPS
I have heard that people use CrystalMark as a quick and dirty way to find out IOPS
Brent Ozar wrote an article about it here: http://www.brentozar.com/archive/2012/03/how-fast-your-san-or-how-slow/
If I want to accommodate 400 Mb/Sec peak IO we currently have, how should I provision AWS EBS volumes? How much provisioned IOPS I should get?
For Throughput:
I'm not familiar with AWS storage provisioning but I checked online on EBS, but it looks like there are some instructions to experiment creating volumes.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/benchmark_piops.html
I'm thinking you could after provisioning volume run SQLIOSIM maybe, capture in perfmon Physical disk counters to measure disk performance.
--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀
July 31, 2015 at 2:38 pm
Great info, thanks a lot, sqlsurfing!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply