@TigerRool10-1 .....Checked your query and test output but this is done at the VM level with the help of Diskspd tool which is Microsoft specific. This forum is exclusively for MSA queries and you need to check Performance for MSA at the block level.
In order to troubleshoot Performance issue, there are many factors involved and it's not straight forward task. Some of the best practice to follow can be no hardware issue should exist, firmware need to be up to date, Connected system like Servers, SAN Switch all need to be up to date with driver/firmware as well.
Need to check what is the block size set at the Host and depends on that we should check if you want high IOPs or high throughput. Specifically, the smaller the I/O size, the more I/Os per second (IOPS) the SAN can process. However, the corollary to this is a decrease in throughput (as measured in MB/s). Conversely, as I/O size increases, IOPS decreases but throughput increases. When an I/O gets above a certain size, latency also increases as the time required to transport each I/O increases such that the disk itself is no longer the major influence on latency.
Typically, workloads can be defined by four categories—I/O size, reads vs. writes, sequential vs. random, and queue depth.
A typical application usually consists of a mix of reads and writes, and sequential and random.
For example, a Microsoft® SQL Server instance running an OLTP type workload might see disk IO that is 8k size, 80 percent read, and 100 percent random.
A disk backup target on the other hand might see disk IO that is 64k or 256K in size, with 90 percent writes and 100 percent sequential.
The type of workload will affect the results of the performance measurement.
Check this below Customer Advisory and disable "In-band SES" ,
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c05306564
You can check the below Customer Advisory as well.........in many situations this helped to improve performance,
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03473698
If you have specific requirement and you want only SSD pages to deal with your IO then use 'Tier Affinity' on the particular volume.
If you still face performance issue then at the time of performance issue happening capture the below outputs atleast 10 to 15 times along with MSA log and log a HPE support case. They will help you.
# show controller-statistics
# show disk-statistics
# show host-port-statistics
# show vdisk-statistics
# show volume-statistics
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
@TigerRool10-1 ......Yes you are correct as of now MSA2040 not yet tested with ESX6.7 so any outcome will be unpredictable.
I do agree with your stress testing but we understand and do the analysis for MSA only in this forum. So application level or OS level testing only Microsoft expert can help you.
If you downgrade to ESX6.5 and use with MSA2040 then kindly follow the instruction that I have suggested, this will help you for sure when you use this MSA for production.
If you still look for more information then kindly mention the same so that MSA experts can help you or else you can close this forum as of now.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
Yes ESX 6.5 U2 not yet tested by HPE with MSA2040
Infact even VMWare website also shows MSA2040 supported upto ESX 6.5 U1
Attached are the screenshots for your reference
Yes GL225R003 is supported with MSA2040 and ESX 6.5 U1
There is no firmware called GL225P001
Please find the link to check all firmware details,
https://h41111.www4.hpe.com/storage/msafirmware.html
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
I work for HPE
