Hello

By default windows systems formats filesystem with 4 KB block size (4096 bytes) witch is not optimized for Microsoft SQL Server.
Best practice is to create different partition on another disk for SQL Server installation (SQL Data files) with 64KB block size.
T-Log can be on other disk with 4KB block because 64K is not necessary.

Lab enviroment:
3x nodes Dell R730XD (1cpu Intex E5-2640 v4, 64 GB Ram, 2x SSD for S2D journal, 4x 10K HDD for capacity, 40Gbit backend traffic)
Windows 2016 S2D storage cluster with three-way mirror, Hyper-v Virtualization

VM test machine (Windows 2016 Server RTM):
4vcpu, 4 GB Ram, 1x OS Disk with 4KB Block size (c:), 1x Data Disk with 4KB Block size (e:), 1x Data Disk with 64 Block Size (f:)

PS C:\Users\Administrator> FSutil FSinfo NTFSinfo c:
NTFS Volume Serial Number :        0xa83eec2c3eebf16c
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x00000000076e47ff
Total Clusters :                   0x0000000000edc8ff
Free Clusters  :                   0x0000000000c04ab9
Total Reserved :                   0x00000000000015b1
Bytes Per Sector  :                512
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024

PS C:\Users\Administrator> FSutil FSinfo NTFSinfo e:
NTFS Volume Serial Number :        0x9820e6ca20e6af06
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x000000000c7befff
Total Clusters :                   0x00000000018f7dff
Free Clusters  :                   0x0000000001195cb1
Total Reserved :                   0x0000000000000400
Bytes Per Sector  :                512
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                4096
Bytes Per FileRecord Segment    :  1024

PS C:\Users\Administrator> FSutil FSinfo NTFSinfo f:
NTFS Volume Serial Number :        0x2616f4e116f4b343
NTFS Version   :                   3.1
LFS Version    :                   2.0
Number Sectors :                   0x000000000c7befff
Total Clusters :                   0x000000000018f7df
Free Clusters  :                   0x000000000012c70d
Total Reserved :                   0x0000000000000040
Bytes Per Sector  :                512
Bytes Per Physical Sector :        4096
Bytes Per Cluster :                65536
Bytes Per FileRecord Segment    :  1024

Test steps:

1. Testing normal OS workload

4KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, without software caching at the operating system level and hardware write caching

Target=E: disk with 4 KB Block

diskspd -b4K -d60 -o4 -t4 -h -r -w25 -L -Z1G -c1G e:\iotest.dat

Result:

actual test time:    60.00s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  23.10%|   1.93%|   21.17%|  76.90%
1|   9.95%|   1.74%|    8.20%|  90.05%
2|  10.18%|   1.95%|    8.23%|  89.81%
3|  11.07%|   2.16%|    8.91%|  88.93%
——————————————-
avg.|  13.57%|   1.95%|   11.63%|  86.42%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1975582720 |       482320 |      31.40 |    8038.22 |    0.496 |     1.127 | e:\iotest.dat (1024MB)
1 |      1975906304 |       482399 |      31.40 |    8039.54 |    0.496 |     1.110 | e:\iotest.dat (1024MB)
2 |      1964466176 |       479606 |      31.22 |    7992.99 |    0.499 |     1.172 | e:\iotest.dat (1024MB)
3 |      1969852416 |       480921 |      31.31 |    8014.91 |    0.498 |     1.105 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total: 7885807616 |      1925246 |     125.33 |   32085.67 |    0.497 |     1.129

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1481773056 |       361761 |      23.55 |    6029.02 |    0.448 |     0.527 | e:\iotest.dat (1024MB)
1 |      1481355264 |       361659 |      23.54 |    6027.32 |    0.447 |     0.507 | e:\iotest.dat (1024MB)
2 |      1473032192 |       359627 |      23.41 |    5993.45 |    0.451 |     0.541 | e:\iotest.dat (1024MB)
3 |      1477066752 |       360612 |      23.48 |    6009.87 |    0.449 |     0.512 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total: 5913227264 |      1443659 |      93.98 |   24059.66 |    0.449 |     0.522

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |       493809664 |       120559 |       7.85 |    2009.21 |    0.642 |     2.054 | e:\iotest.dat (1024MB)
1 |       494551040 |       120740 |       7.86 |    2012.22 |    0.643 |     2.030 | e:\iotest.dat (1024MB)
2 |       491433984 |       119979 |       7.81 |    1999.54 |    0.643 |     2.142 | e:\iotest.dat (1024MB)
3 |       492785664 |       120309 |       7.83 |    2005.04 |    0.645 |     2.016 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total: 1972580352 |       481587 |      31.35 |    8026.01 |    0.643 |     2.061

 


4KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, with software caching at the operating system level and hardware write caching

Target=E: disk with 4 KB Block

diskspd -b4K -d60 -o4 -t4 -r -w25 -L -Z1G -c1G e:\iotest.dat

actual test time:    60.00s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  76.07%|   5.00%|   71.07%|  23.93%
1|  76.64%|   5.89%|   70.76%|  23.36%
2|  65.99%|   4.22%|   61.77%|  34.01%
3|  76.98%|   5.60%|   71.38%|  23.02%
——————————————-
avg.|  73.92%|   5.18%|   68.74%|  26.08%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     14675480576 |      3582881 |     233.26 |   59714.74 |    0.066 |     0.147 | e:\iotest.dat (1024MB)
1 |     14894460928 |      3636343 |     236.74 |   60605.77 |    0.065 |     0.135 | e:\iotest.dat (1024MB)
2 |     14504267776 |      3541081 |     230.54 |   59018.07 |    0.067 |     0.139 | e:\iotest.dat (1024MB)
3 |     14666862592 |      3580777 |     233.12 |   59679.67 |    0.066 |     0.080 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  58741071872 |     14341082 |     933.67 |  239018.24 |    0.066 |     0.128

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     11008675840 |      2687665 |     174.98 |   44794.46 |    0.066 |     0.142 | e:\iotest.dat (1024MB)
1 |     11164770304 |      2725774 |     177.46 |   45429.61 |    0.065 |     0.150 | e:\iotest.dat (1024MB)
2 |     10872004608 |      2654298 |     172.81 |   44238.34 |    0.067 |     0.140 | e:\iotest.dat (1024MB)
3 |     10995724288 |      2684503 |     174.77 |   44741.76 |    0.066 |     0.078 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:   44041175040 |     10752240 |     700.02 |  179204.16 |    0.066 |     0.131

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      3666804736 |       895216 |      58.28 |   14920.28 |    0.068 |     0.164 | e:\iotest.dat (1024MB)
1 |      3729690624 |       910569 |      59.28 |   15176.16 |    0.066 |     0.071 | e:\iotest.dat (1024MB)
2 |      3632263168 |       886783 |      57.73 |   14779.73 |    0.068 |     0.136 | e:\iotest.dat (1024MB)
3 |      3671138304 |       896274 |      58.35 |   14937.91 |    0.067 |     0.086 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:   14699896832 |      3588842 |     233.65 |   59814.09 |    0.067 |     0.120


 

4KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, without software caching at the operating system level and hardware write caching

Target=F: disk with 64 KB Block

diskspd -b4K -d60 -o4 -t4 -h -r -w25 -L -Z1G -c1G f:\iotest.dat

actual test time:    60.01s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  23.98%|   1.82%|   22.16%|  76.01%
1|  10.68%|   1.82%|    8.85%|  89.31%
2|  12.45%|   2.81%|    9.63%|  87.54%
3|  10.88%|   1.64%|    9.24%|  89.11%
——————————————-
avg.|  14.50%|   2.02%|   12.47%|  85.49%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1993539584 |       486704 |      31.68 |    8111.00 |    0.492 |     0.914 | f:\iotest.dat (1024MB)
1 |      1979899904 |       483374 |      31.47 |    8055.50 |    0.495 |     0.938 | f:\iotest.dat (1024MB)
2 |      1971879936 |       481416 |      31.34 |    8022.87 |    0.497 |     0.931 | f:\iotest.dat (1024MB)
3 |      1976737792 |       482602 |      31.42 |    8042.64 |    0.496 |     0.920 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   7922057216 |      1934096 |     125.91 |   32232.01 |    0.495 |     0.926

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1495547904 |       365124 |      23.77 |    6084.85 |    0.437 |     0.512 | f:\iotest.dat (1024MB)
1 |      1484271616 |       362371 |      23.59 |    6038.97 |    0.441 |     0.511 | f:\iotest.dat (1024MB)
2 |      1478897664 |       361059 |      23.50 |    6017.10 |    0.443 |     0.532 | f:\iotest.dat (1024MB)
3 |      1482084352 |       361837 |      23.55 |    6030.07 |    0.441 |     0.519 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   5940801536 |      1450391 |      94.42 |   24170.99 |    0.441 |     0.519

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |       497991680 |       121580 |       7.91 |    2026.15 |    0.656 |     1.588 | f:\iotest.dat (1024MB)
1 |       495628288 |       121003 |       7.88 |    2016.53 |    0.657 |     1.643 | f:\iotest.dat (1024MB)
2 |       492982272 |       120357 |       7.84 |    2005.77 |    0.661 |     1.606 | f:\iotest.dat (1024MB)
3 |       494653440 |       120765 |       7.86 |    2012.57 |    0.659 |     1.594 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   1981255680 |       483705 |      31.49 |    8061.02 |    0.658 |     1.608


 

4KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, with software caching at the operating system level and hardware write caching

Target=F: disk with 64 KB Block

diskspd -b4K -d60 -o4 -t4  -r -w25 -L -Z1G -c1G f:\iotest.dat

actual test time:    60.02s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  74.43%|   5.15%|   69.28%|  25.57%
1|  59.41%|   2.84%|   56.57%|  40.59%
2|  74.77%|   4.74%|   70.03%|  25.23%
3|  75.55%|   5.18%|   70.37%|  24.45%
——————————————-
avg.|  71.04%|   4.48%|   66.56%|  28.96%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     14814429184 |      3616804 |     235.41 |   60264.45 |    0.066 |     0.071 | f:\iotest.dat (1024MB)
1 |     14767001600 |      3605225 |     234.65 |   60071.52 |    0.066 |     0.057 | f:\iotest.dat (1024MB)
2 |     14502645760 |      3540685 |     230.45 |   58996.13 |    0.067 |     0.109 | f:\iotest.dat (1024MB)
3 |     14751698944 |      3601489 |     234.41 |   60009.27 |    0.066 |     0.055 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  58835775488 |     14364203 |     934.93 |  239341.38 |    0.066 |     0.076

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     11113254912 |      2713197 |     176.59 |   45208.24 |    0.066 |     0.073 | f:\iotest.dat (1024MB)
1 |     11069140992 |      2702427 |     175.89 |   45028.78 |    0.066 |     0.058 | f:\iotest.dat (1024MB)
2 |     10870800384 |      2654004 |     172.74 |   44221.94 |    0.067 |     0.107 | f:\iotest.dat (1024MB)
3 |     11059560448 |      2700088 |     175.74 |   44989.81 |    0.066 |     0.056 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  44112756736 |     10769716 |     700.97 |  179448.78 |    0.066 |     0.076

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      3701174272 |       903607 |      58.81 |   15056.22 |    0.067 |     0.066 | f:\iotest.dat (1024MB)
1 |      3697860608 |       902798 |      58.76 |   15042.74 |    0.067 |     0.053 | f:\iotest.dat (1024MB)
2 |      3631845376 |       886681 |      57.71 |   14774.19 |    0.068 |     0.113 | f:\iotest.dat (1024MB)
3 |      3692138496 |       901401 |      58.67 |   15019.46 |    0.067 |     0.053 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   14723018752 |      3594487 |     233.96 |   59892.60 |    0.067 |     0.075


2. Testing MS SQL data file workload

8KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, without software caching at the operating system level and hardware write caching

Target=e: disk with 4 KB Block

diskspd -b8K -d60 -o4 -t4 -h -r -w25 -L -Z1G -c1G e:\iotest.dat

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  17.11%|   1.38%|   15.73%|  82.89%
1|   7.32%|   1.25%|    6.07%|  92.68%
2|   7.86%|   1.54%|    6.33%|  92.13%
3|   7.24%|   1.17%|    6.07%|  92.76%
——————————————-
avg.|   9.88%|   1.33%|    8.55%|  90.11%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      2894110720 |       353285 |      46.00 |    5887.82 |    0.678 |     0.885 | e:\iotest.dat (1024MB)
1 |      2881167360 |       351705 |      45.79 |    5861.49 |    0.681 |     0.884 | e:\iotest.dat (1024MB)
2 |      2861113344 |       349257 |      45.47 |    5820.69 |    0.686 |     0.895 | e:\iotest.dat (1024MB)
3 |      2871009280 |       350465 |      45.63 |    5840.82 |    0.684 |     0.884 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  11507400704 |      1404712 |     182.90 |   23410.83 |    0.682 |     0.887

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      2171445248 |       265069 |      34.51 |    4417.62 |    0.705 |     0.741 | e:\iotest.dat (1024MB)
1 |      2160394240 |       263720 |      34.34 |    4395.14 |    0.709 |     0.737 | e:\iotest.dat (1024MB)
2 |      2147188736 |       262108 |      34.13 |    4368.27 |    0.713 |     0.744 | e:\iotest.dat (1024MB)
3 |      2150285312 |       262486 |      34.18 |    4374.57 |    0.711 |     0.740 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  8629313536 |      1053383 |     137.15 |   17555.60 |    0.709 |     0.741

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |       722665472 |        88216 |      11.49 |    1470.20 |    0.595 |     1.216 | e:\iotest.dat (1024MB)
1 |       720773120 |        87985 |      11.46 |    1466.35 |    0.599 |     1.220 | e:\iotest.dat (1024MB)
2 |       713924608 |        87149 |      11.35 |    1452.42 |    0.605 |     1.239 | e:\iotest.dat (1024MB)
3 |       720723968 |        87979 |      11.46 |    1466.25 |    0.603 |     1.212 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  2878087168 |       351329 |      45.74 |    5855.22 |    0.600 |     1.222


 

8KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, with software caching at the operating system level and hardware write caching

Target=e: disk with 4 KB Block

diskspd -b8K -d60 -o4 -t4  -r -w25 -L -Z1G -c1G e:\iotest.dat

actual test time:    60.00s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  73.62%|   5.08%|   68.54%|  26.38%
1|  75.08%|   4.35%|   70.73%|  24.90%
2|  64.40%|   3.46%|   60.94%|  35.60%
3|  74.14%|   4.06%|   70.08%|  25.86%
——————————————-
avg.|  71.81%|   4.24%|   67.57%|  28.18%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     25919823872 |      3164041 |     411.98 |   52734.03 |    0.075 |     0.079 | e:\iotest.dat (1024MB)
1 |     25327026176 |      3091678 |     402.56 |   51527.98 |    0.077 |     0.067 | e:\iotest.dat (1024MB)
2 |     25062055936 |      3059333 |     398.35 |   50988.89 |    0.078 |     0.093 | e:\iotest.dat (1024MB)
3 |     25635676160 |      3129355 |     407.47 |   52155.93 |    0.076 |     0.063 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  101944582144 |     12444407 |    1620.37 |  207406.82 |    0.077 |     0.076

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     19444498432 |      2373596 |     309.06 |   39559.94 |    0.075 |     0.080 | e:\iotest.dat (1024MB)
1 |     18980118528 |      2316909 |     301.68 |   38615.16 |    0.076 |     0.067 | e:\iotest.dat (1024MB)
2 |     18787368960 |      2293380 |     298.62 |   38223.01 |    0.077 |     0.093 | e:\iotest.dat (1024MB)
3 |     19220930560 |      2346305 |     305.51 |   39105.09 |    0.076 |     0.063 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  76432916480 |      9330190 |    1214.87 |  155503.20 |    0.076 |     0.076

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      6475325440 |       790445 |     102.92 |   13174.09 |    0.077 |     0.077 | e:\iotest.dat (1024MB)
1 |      6346907648 |       774769 |     100.88 |   12912.82 |    0.079 |     0.066 | e:\iotest.dat (1024MB)
2 |      6274686976 |       765953 |      99.73 |   12765.89 |    0.079 |     0.092 | e:\iotest.dat (1024MB)
3 |      6414745600 |       783050 |     101.96 |   13050.84 |    0.078 |     0.065 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  25511665664 |      3114217 |     405.50 |   51903.63 |    0.078 |     0.076



8KB Block size
, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, without software caching at the operating system level and hardware write caching

Target=f: disk with 64 KB Block

diskspd -b8K -d60 -o4 -t4 -h -r -w25 -L -Z1G -c1G f:\iotest.dat

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  19.22%|   1.74%|   17.47%|  80.78%
1|   8.54%|   1.38%|    7.16%|  91.46%
2|   8.33%|   1.41%|    6.93%|  91.66%
3|   8.02%|   1.46%|    6.56%|  91.95%
——————————————-
avg.|  11.03%|   1.50%|    9.53%|  88.96%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      3087974400 |       376950 |      49.08 |    6282.37 |    0.635 |     0.969 | f:\iotest.dat (1024MB)
1 |      3075989504 |       375487 |      48.89 |    6257.99 |    0.638 |     0.973 | f:\iotest.dat (1024MB)
2 |      3055394816 |       372973 |      48.56 |    6216.09 |    0.642 |     0.982 | f:\iotest.dat (1024MB)
3 |      3070509056 |       374818 |      48.80 |    6246.84 |    0.639 |     1.031 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  12289867776 |      1500228 |     195.34 |   25003.29 |    0.639 |     0.989

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      2317180928 |       282859 |      36.83 |    4714.22 |    0.645 |     0.648 | f:\iotest.dat (1024MB)
1 |      2305720320 |       281460 |      36.65 |    4690.90 |    0.648 |     0.644 | f:\iotest.dat (1024MB)
2 |      2292482048 |       279844 |      36.44 |    4663.97 |    0.653 |     0.678 | f:\iotest.dat (1024MB)
3 |      2300518400 |       280825 |      36.57 |    4680.32 |    0.649 |     0.654 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  9215901696 |      1124988 |     146.48 |   18749.41 |    0.649 |     0.656

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |       770793472 |        94091 |      12.25 |    1568.15 |    0.607 |     1.581 | f:\iotest.dat (1024MB)
1 |       770269184 |        94027 |      12.24 |    1567.08 |    0.609 |     1.594 | f:\iotest.dat (1024MB)
2 |       762912768 |        93129 |      12.13 |    1552.12 |    0.610 |     1.575 | f:\iotest.dat (1024MB)
3 |       769990656 |        93993 |      12.24 |    1566.52 |    0.609 |     1.721 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   3073966080 |       375240 |      48.86 |    6253.87 |    0.609 |     1.619


8KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, random, 25 % Write, 75 % Read, with software caching at the operating system level and hardware write caching

Target=f: disk with 64 KB Block

diskspd -b8K -d60 -o4 -t4  -r -w25 -L -Z1G -c1G f:\iotest.dat

actual test time:    60.02s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|  66.83%|   2.94%|   63.89%|  33.17%
1|  75.76%|   4.22%|   71.54%|  24.24%
2|  74.33%|   4.30%|   70.03%|  25.67%
3|  74.62%|   4.35%|   70.27%|  25.38%
——————————————-
avg.|  72.88%|   3.95%|   68.93%|  27.12%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     26137509888 |      3190614 |     415.34 |   53163.13 |    0.075 |     0.075 | f:\iotest.dat (1024MB)
1 |     25768189952 |      3145531 |     409.47 |   52411.94 |    0.076 |     0.055 | f:\iotest.dat (1024MB)
2 |     25579544576 |      3122503 |     406.47 |   52028.24 |    0.076 |     0.098 | f:\iotest.dat (1024MB)
3 |     25740943360 |      3142205 |     409.04 |   52356.52 |    0.076 |     0.057 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  103226187776 |     12600853 |    1640.31 |  209959.83 |    0.076 |     0.073

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |     19607953408 |      2393549 |     311.58 |   39882.15 |    0.074 |     0.073 | f:\iotest.dat (1024MB)
1 |     19311239168 |      2357329 |     306.86 |   39278.64 |    0.075 |     0.054 | f:\iotest.dat (1024MB)
2 |     19175194624 |      2340722 |     304.70 |   39001.93 |    0.076 |     0.098 | f:\iotest.dat (1024MB)
3 |     19300229120 |      2355985 |     306.69 |   39256.25 |    0.075 |     0.057 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  77394616320 |      9447585 |    1229.84 |  157418.97 |    0.075 |     0.073

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      6529556480 |       797065 |     103.76 |   13280.98 |    0.076 |     0.078 | f:\iotest.dat (1024MB)
1 |      6456950784 |       788202 |     102.60 |   13133.30 |    0.077 |     0.059 | f:\iotest.dat (1024MB)
2 |      6404349952 |       781781 |     101.77 |   13026.31 |    0.078 |     0.099 | f:\iotest.dat (1024MB)
3 |      6440714240 |       786220 |     102.35 |   13100.27 |    0.077 |     0.060 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  25831571456 |      3153268 |     410.48 |   52540.86 |    0.077 |     0.076


3. Testing MS SQL T-Log workload

64KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, seq, 100 % Write, 0 % Read, without software caching at the operating system level and hardware write caching

Target=e: disk with 4 KB Block

diskspd -b64K -d60 -o4 -t4 -h -si -w100 -L -Z1G -c1G e:\iotest.dat

actual test time:    60.01s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|   5.13%|   0.42%|    4.71%|  94.88%
1|   2.29%|   0.34%|    1.95%|  97.72%
2|   3.41%|   0.78%|    2.63%|  96.60%
3|   2.42%|   0.49%|    1.93%|  97.59%
——————————————-
avg.|   3.31%|   0.51%|    2.81%|  96.69%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5195497472 |        79277 |      82.57 |    1321.05 |    3.027 |     2.313 | e:\iotest.dat (1024MB)
1 |      5202444288 |        79383 |      82.68 |    1322.81 |    3.023 |     2.306 | e:\iotest.dat (1024MB)
2 |      5162008576 |        78766 |      82.03 |    1312.53 |    3.046 |     2.367 | e:\iotest.dat (1024MB)
3 |      5200805888 |        79358 |      82.65 |    1322.39 |    3.024 |     2.323 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  20760756224 |       316784 |     329.92 |    5278.78 |    3.030 |     2.327

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | e:\iotest.dat (1024MB)
1 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | e:\iotest.dat (1024MB)
2 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | e:\iotest.dat (1024MB)
3 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:              0 |            0 |       0.00 |       0.00 |    0.000 |       N/A

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5195497472 |        79277 |      82.57 |    1321.05 |    3.027 |     2.313 | e:\iotest.dat (1024MB)
1 |      5202444288 |        79383 |      82.68 |    1322.81 |    3.023 |     2.306 | e:\iotest.dat (1024MB)
2 |      5162008576 |        78766 |      82.03 |    1312.53 |    3.046 |     2.367 | e:\iotest.dat (1024MB)
3 |      5200805888 |        79358 |      82.65 |    1322.39 |    3.024 |     2.323 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:   20760756224 |       316784 |     329.92 |    5278.78 |    3.030 |     2.327


 

64KB Block size, 4 Worker threads, 4 Outstanding I/Os per target, seq, 100 % Write, 0 % Read, without software caching at the operating system level and hardware write caching

Target=f: disk with 64 KB Block

diskspd -b64K -d60 -o4 -t4 -h -si -w100 -L -Z1G -c1G f:\iotest.dat

actual test time:    60.02s
thread count:        4
proc count:        4

CPU |  Usage |  User  |  Kernel |  Idle
——————————————-
0|   6.20%|   1.02%|    5.18%|  93.80%
1|   3.23%|   0.81%|    2.42%|  96.77%
2|   2.89%|   0.55%|    2.34%|  97.11%
3|   3.38%|   0.78%|    2.60%|  96.62%
——————————————-
avg.|   3.92%|   0.79%|    3.14%|  96.08%

Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5218304000 |        79625 |      82.92 |    1326.75 |    3.014 |     2.318 | f:\iotest.dat (1024MB)
1 |      5196283904 |        79289 |      82.57 |    1321.15 |    3.026 |     2.326 | f:\iotest.dat (1024MB)
2 |      5171380224 |        78909 |      82.18 |    1314.82 |    3.041 |     2.374 | f:\iotest.dat (1024MB)
3 |      5191565312 |        79217 |      82.50 |    1319.95 |    3.029 |     2.367 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  20777533440 |       317040 |     330.17 |    5282.66 |    3.027 |     2.346

Read IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | f:\iotest.dat (1024MB)
1 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | f:\iotest.dat (1024MB)
2 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | f:\iotest.dat (1024MB)
3 |               0 |            0 |       0.00 |       0.00 |    0.000 |       N/A | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:              0 |            0 |       0.00 |       0.00 |    0.000 |       N/A

Write IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5218304000 |        79625 |      82.92 |    1326.75 |    3.014 |     2.318 | f:\iotest.dat (1024MB)
1 |      5196283904 |        79289 |      82.57 |    1321.15 |    3.026 |     2.326 | f:\iotest.dat (1024MB)
2 |      5171380224 |        78909 |      82.18 |    1314.82 |    3.041 |     2.374 | f:\iotest.dat (1024MB)
3 |      5191565312 |        79217 |      82.50 |    1319.95 |    3.029 |     2.367 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  20777533440 |       317040 |     330.17 |    5282.66 |    3.027 |     2.346


 

Conclusion:

1. Normal OS workload

There is no differences between 4KB block size and 64KB Block size

4KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1975582720 |       482320 |      31.40 |    8038.22 |    0.496 |     1.127 | e:\iotest.dat (1024MB)
1 |      1975906304 |       482399 |      31.40 |    8039.54 |    0.496 |     1.110 | e:\iotest.dat (1024MB)
2 |      1964466176 |       479606 |      31.22 |    7992.99 |    0.499 |     1.172 | e:\iotest.dat (1024MB)
3 |      1969852416 |       480921 |      31.31 |    8014.91 |    0.498 |     1.105 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total: 7885807616 |      1925246 |     125.33 |   32085.67 |    0.497 |     1.129

64KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      1993539584 |       486704 |      31.68 |    8111.00 |    0.492 |     0.914 | f:\iotest.dat (1024MB)
1 |      1979899904 |       483374 |      31.47 |    8055.50 |    0.495 |     0.938 | f:\iotest.dat (1024MB)
2 |      1971879936 |       481416 |      31.34 |    8022.87 |    0.497 |     0.931 | f:\iotest.dat (1024MB)
3 |      1976737792 |       482602 |      31.42 |    8042.64 |    0.496 |     0.920 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:   7922057216 |      1934096 |     125.91 |   32232.01 |    0.495 |     0.926

 

2. MS SQL data file workload

There is differences between 4KB block size and 64KB Block size. This is only lab environment but in real production the differences are about 20 percents at IO and latency lvl.

4KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      2894110720 |       353285 |      46.00 |    5887.82 |    0.678 |     0.885 | e:\iotest.dat (1024MB)
1 |      2881167360 |       351705 |      45.79 |    5861.49 |    0.681 |     0.884 | e:\iotest.dat (1024MB)
2 |      2861113344 |       349257 |      45.47 |    5820.69 |    0.686 |     0.895 | e:\iotest.dat (1024MB)
3 |      2871009280 |       350465 |      45.63 |    5840.82 |    0.684 |     0.884 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  11507400704 |      1404712 |     182.90 |   23410.83 |    0.682 |     0.887

64KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      3087974400 |       376950 |      49.08 |    6282.37 |    0.635 |     0.969 | f:\iotest.dat (1024MB)
1 |      3075989504 |       375487 |      48.89 |    6257.99 |    0.638 |     0.973 | f:\iotest.dat (1024MB)
2 |      3055394816 |       372973 |      48.56 |    6216.09 |    0.642 |     0.982 | f:\iotest.dat (1024MB)
3 |      3070509056 |       374818 |      48.80 |    6246.84 |    0.639 |     1.031 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  12289867776 |      1500228 |     195.34 |   25003.29 |    0.639 |     0.989

3. MS SQL T-Log workload

There is no differences between 4KB block size and 64KB Block size

4KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5195497472 |        79277 |      82.57 |    1321.05 |    3.027 |     2.313 | e:\iotest.dat (1024MB)
1 |      5202444288 |        79383 |      82.68 |    1322.81 |    3.023 |     2.306 | e:\iotest.dat (1024MB)
2 |      5162008576 |        78766 |      82.03 |    1312.53 |    3.046 |     2.367 | e:\iotest.dat (1024MB)
3 |      5200805888 |        79358 |      82.65 |    1322.39 |    3.024 |     2.323 | e:\iotest.dat (1024MB)
—————————————————————————————————–
total:  20760756224 |       316784 |     329.92 |    5278.78 |    3.030 |     2.327

64KB:
Total IO
thread |       bytes     |     I/Os     |     MB/s   |  I/O per s |  AvgLat  | LatStdDev |  file
—————————————————————————————————–
0 |      5218304000 |        79625 |      82.92 |    1326.75 |    3.014 |     2.318 | f:\iotest.dat (1024MB)
1 |      5196283904 |        79289 |      82.57 |    1321.15 |    3.026 |     2.326 | f:\iotest.dat (1024MB)
2 |      5171380224 |        78909 |      82.18 |    1314.82 |    3.041 |     2.374 | f:\iotest.dat (1024MB)
3 |      5191565312 |        79217 |      82.50 |    1319.95 |    3.029 |     2.367 | f:\iotest.dat (1024MB)
—————————————————————————————————–
total:  20777533440 |       317040 |     330.17 |    5282.66 |    3.027 |     2.346

 

The Lab was created with the help of infra team CNC, a.s. especially Rado, Tomas, Steino, Dano, Peter (Installation Support)

Special thanks to Jaro and Dell Team Slovakia (HW equipment)

Reklamy

Hi

I wanted to add a new LUN with metro mirror remote copy yesterday, however:

My Storage told me:

CMMVC5970E The Remote Copy relationship was not created because there is not enough memory.

I’ve tried to search this message on google but I’ve not found anything except below Explanation:

Explanation

The Remote Copy relationship was not created because there is not enough memory.

Action

Not applicable.

Source: http://www-01.ibm.com/support/knowledgecenter/STPVGU_5.1.0/com.ibm.storage.svc.console.510.doc/msg_cmmvc5970e.html?lang=en

I contacted IBM support a we found solution:

IBM_Storwize:v3700Primary:mike>lsiogrp 0
id 0
name io_grp0
node_count 2
vdisk_count 37
host_count 6
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 1.8MB
mirroring_total_memory 20.0MB
mirroring_free_memory 20.0MB
raid_total_memory 40.0MB
raid_free_memory 21.6MB
maintenance no
compression_active no
accessible_vdisk_count 37
compression_supported no

IBM_Storwize:v3700Primary:mike>chiogrp -feature remote -size 30 io_grp0

IBM_Storwize:v3700primary:mike>lsiogrp 0
id 0
name io_grp0
node_count 2
vdisk_count 37
host_count 6
flash_copy_total_memory 20.0MB
flash_copy_free_memory 20.0MB
remote_copy_total_memory 30.0MB
remote_copy_free_memory 11.8MB
mirroring_total_memory 20.0MB
mirroring_free_memory 20.0MB
raid_total_memory 40.0MB
raid_free_memory 21.6MB
maintenance no
compression_active no
accessible_vdisk_count 37
compression_supported no

This solution must be applicated on both storages. (Primary and Aux)

Best Regards

Mike

Hi

Our customer uncheck from “Default Role Assignment Policy” role “MyBaseOptions” .

This had an impact to/caused – All users from customer organization didn’t have a permissions to ECP web site.

Solution:

New-ManagementRoleAssignment -organization mysexycustomer.sk -Role MyBaseOptions -Policy “Default Role Assignment Policy”

This command adds role MyBaseOptions to default policy a ecp works again 🙂

In case of presist malfunction right after command, try to wait 15 minutes.

 

Have a nice day

Miro

Dear colleagues

Few days ago, I’ve struggled with the settings of Outlook Anywhere via TMG 2010. Everything was OK, however the OAB and mailtips didn’t work. I don’t prefer split of dns scenarios, so I usually use domain.local and domain.external zones. Publishing exchange 2013 is different than exchnage 2010 which means that your internal domain URL must be set as external.

For short example see below:

Get-WebservicesVirtualDirectory -Server domain\casserver | Set-WebservicesVirtualDirectory -InternalURL https://mail.yourexternaldomain.com/EWS/Exchange.asmx -ExternalURL https://mail.yourexternaldomain.com/EWS/Exchange.asmx

Get-OwaVirtualDirectory -Server domain\casserver | Set-OwaVirtualDirectory -InternalURL https://mail.yourexternaldomain.com/owa -ExternalURL https://mail.yourexternaldomain.com/owa

Get-ecpVirtualDirectory -Server domain\casserver | Set-ecpVirtualDirectory -InternalURL https://mail.yourexternaldomain.com/ecp -ExternalURL https://mail.yourexternaldomain.com/ecp

Get-ActiveSyncVirtualDirectory -Server domain\casserver | Set-ActiveSyncVirtualDirectory -InternalURL https://mail.yourexternaldomain.com/Microsoft-Server-ActiveSync -ExternalURL https://mail.yourexternaldomain.com/Microsoft-Server-ActiveSync

Get-OABVirtualDirectory -Server domain\casserver | Set-OABVirtualDirectory -InternalUrl https://mail.yourexternaldomain.com/OAB -ExternalURL https://mail.yourexternaldomain.com/OAB

Set-ClientAccessServer domain\casserver -AutodiscoverServiceInternalUri https://mail.yourexternaldomain.com/Autodiscover/Autodiscover.xml

Set-OutlookAnywhere -Identity “domain\casserver\Rpc (Default Web Site)” -InternalHostname mail.yourexternaldomain.com -ExternalHostName mail.yourexternaldomain.com -InternalClientAuthenticationMethod ntlm -InternalClientsRequireSsl:$True -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl:$True

Moreover, there is one more difference within TMG settings:

1. /EWS/* , /OAB/* and /rpc/* must be set to NO DELEGATION, BUT CLIENT MAY AUTHENTICATE DIRECTLY
2. Users set to ALL USERS

Do not hesitate to contact me or any additional comments are welcome.

Best regards

Miroslav

 

Hi friends

Today we will show how to repair corrupted MSDB database.

When we have an error in windows event viewer something like this:

Unable to find index entry in index ID 1, of table 149575571, in database ‘msdb’. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.

We need execute query in MS sql studio:

dbcc checkdb(‘msdb’) with no_infomsgs

when we have some errors we need to use this command

USE [master]
GO
ALTER DATABASE [msdb] SET  SINGLE_USER WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE [msdb] SET  SINGLE_USER
GO
DBCC CHECKDB (msdb, REPAIR_ALLOW_DATA_LOSS)
GO
ALTER DATABASE [msdb] SET  MULTI_USER

After this query we run again:

dbcc checkdb(‘msdb’) with no_infomsgs

And we are done… 🙂

After that do full backup of all databases or backup only MSDB its on your decision

Best regards

Miro Hlavaty

Hi!!

Today we will show how to repair corrupted MS SQL database.

In MS SQL Studio run new query:

1. dbcc checkdb(‘DB-NAME’) with no_infomsgs

DB-NAME is a name of your corrupted database. If this is completed without any errors then the database does not need to be repaired.

2. Alter database DB-NAME set SINGLE_USER

Before we begin repairing the database, the database must be set in single user mode.

3. dbcc checkdb(‘DB-NAME’,REPAIR_REBUILD)

There are number of repair model usually we use first REPAIR_REBUILD. When everything is ok go to step 5.e (multi user mode) If not, go to next step.

4. dbcc checkdb(‘DB-NAME’,REPAIR_ALLOW_DATA_LOSS)

This command may cause data loss. When everything is ok go to step 5.e (multi user mode) If not, go to next step.

5.

a. ALTER DATABASE DB-NAME SET EMERGENCY
b. ALTER DATABASE DB-NAME SET SINGLE_USER
c. DBCC CHECKDB (DB-NAME, REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS, ALL_ERRORMSGS
d. ALTER DATABASE DB-NAME SET ONLINE
e. ALTER database DB-NAME set MULTI_USER

Description:
a. Set database to emergency mode
b. Set database to single user mode
c. Check database and repair with allow data loss
d. Back database to online mode from emergency mode
e. Set database to multi user mode for normal use

Best regards

Miroslav Hlavaty

Hello

Today we show how to make windows 2008 restore in recovery mode from a network share on the virtual machine runs on VMware. Assuming that we use E1000 network card windows does not set the IP address. Run the command line:

1. C:\Users\Administrator>wpeinit   (This command load network driver for our E1000)

2. C:\Users\Administrator> netsh interface ipv4 show interfaces (This command show interfaces)

Example:

Idx  Met   MTU   State        Name
—  —  —–  ———–  ——————-
1   50 4294967295  connected    Loopback Pseudo-Interface 1
10   20   1500  connected    Local Area Connection

3. C:\Users\Administrator>netsh interface ipv4 set address name=”Local Area Connection” source=static address=192.168.1.11 mask=255.255.255.0 gateway=192.168.1.1  (This command add IP address to interface Local Area Connecion)

After that procedure now we can access to network share.

Best regards

Miro