12 August,2011 by Tom Collins
The Storage \ SAN administrator asks “ can I have some targets to aim for in testing a new storage IO subsystem installation” . Of course , as the SQL Server DBA I normally reply by saying “ I don’t have any targets apart from activity type and optimal targets – such as - less than 5 ms for OLTP data activity”
As a DBA I’m interested in these optimal rates . How the storage experts architect the system is their problem .
In reality , the DBA has to work with the storage team. Storage is a critical aspect of optimising IO throughput . Use Logical Disk:Disk Writes/Sec and Logical Disk: Disk Reads/Sec to estimate IOPs required by the application
This t-sql code calculates the MB/sec . The inputs are IO per second and block size. In the example below : 450 IOs per second at a 8KB block size gives as 3.52 MB/sec.
This allows the DBA and the storage expert to calculate optimal configurations. Play around with the inputs for different targets. Such as 32 , 64, 128, 256 block size
declare @iosec decimal(10,2); declare @byte_size decimal(10,2); declare @total decimal(10,2); set @iosec = 450.00; set @byte_size = 8.00; set @total = 0.00; set @total = ((@iosec * (@byte_size * 1024)) / 1024) / 1024; print @total;
Byte Size (KB) |
IO/sec |
MB/Sec |
8 |
450 |
3.54 |
Author: Jack Vamvas (http://www.sqlserver-dba.com)
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |