- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: scsi queue depth usage
Operating System - HP-UX
1753914
Members
9104
Online
108810
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2011 05:32 AM
тАО04-12-2011 05:32 AM
Hi,
I'm trying to find the usage of the scsi queue depth for a disk. I know I can find the limit of the scsi queue depth using scsimgr but I'm trying to find the actual usage of the scsi queue depth.
Is the BYDSK_REQUEST_QUEUE measureare metric related to the scsi queue depth value ?
Thanks
Michael
I'm trying to find the usage of the scsi queue depth for a disk. I know I can find the limit of the scsi queue depth using scsimgr but I'm trying to find the actual usage of the scsi queue depth.
Is the BYDSK_REQUEST_QUEUE measureare metric related to the scsi queue depth value ?
Thanks
Michael
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2011 08:00 AM
тАО04-12-2011 08:00 AM
Solution
Michael,
No BYDSK_REQUEST_QUEUE shows IOs which are queueing waiting to be sent to the LUN, wheeras a SCSI queue depth is the total amount of IOs that can be outstanding on the LUN (i.e. already sent to the SCSI target) - does that make sense?
I don't think there's any way to easily see what the current number of outstanding IOs are on any given LUN, but you can check if the queue for the target port the LUN is on filled up or not using a scsimgr command such as this:
# scsimgr get_stat -D /dev/rdisk/disk11 all_lpt | grep -E 'Queue full|STATISTICS'
STATISTICS FOR LUN path : lunpath12
Queue full status = 0
STATISTICS FOR LUN path : lunpath17
Queue full status = 0
STATISTICS FOR LUN path : lunpath11
Queue full status = 0
STATISTICS FOR LUN path : lunpath20
Queue full status = 0
So since I reset my scsimgr stats using the command "scsimgr clear_stat ..." I haven't seen any "queue full events returned by any of the paths to the LUN. However I don't think this stat necessarily relates to what the SCSI queue depth is set to on the host, but rather to what the target port can actually handle (I say "don't think" as I'm not completely sure). So for example I might have 10 LUNs presented out of an EVAx400 controller port with a queue depth set to say 128 - that would mean I could in theory have 10 x 128 = 1280 IOs outstanding on that port before IOs start to get queued up (assuming perfectly symmetric IOs across the LUNs), but I happen to know that the maximum target port queue size for an EVAx400 controller port is 1536, so I don't think I would see a "Queue full" status in my scsimgr output in this case anyway.
Rather than worrying too much about this yourself, you might want to think about getting HP-UX to do this heavy lifting for you - have a read of the following white paper:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02054623/c02054623.pdf
HTH
Duncan
I am an HPE Employee
No BYDSK_REQUEST_QUEUE shows IOs which are queueing waiting to be sent to the LUN, wheeras a SCSI queue depth is the total amount of IOs that can be outstanding on the LUN (i.e. already sent to the SCSI target) - does that make sense?
I don't think there's any way to easily see what the current number of outstanding IOs are on any given LUN, but you can check if the queue for the target port the LUN is on filled up or not using a scsimgr command such as this:
# scsimgr get_stat -D /dev/rdisk/disk11 all_lpt | grep -E 'Queue full|STATISTICS'
STATISTICS FOR LUN path : lunpath12
Queue full status = 0
STATISTICS FOR LUN path : lunpath17
Queue full status = 0
STATISTICS FOR LUN path : lunpath11
Queue full status = 0
STATISTICS FOR LUN path : lunpath20
Queue full status = 0
So since I reset my scsimgr stats using the command "scsimgr clear_stat ..." I haven't seen any "queue full events returned by any of the paths to the LUN. However I don't think this stat necessarily relates to what the SCSI queue depth is set to on the host, but rather to what the target port can actually handle (I say "don't think" as I'm not completely sure). So for example I might have 10 LUNs presented out of an EVAx400 controller port with a queue depth set to say 128 - that would mean I could in theory have 10 x 128 = 1280 IOs outstanding on that port before IOs start to get queued up (assuming perfectly symmetric IOs across the LUNs), but I happen to know that the maximum target port queue size for an EVAx400 controller port is 1536, so I don't think I would see a "Queue full" status in my scsimgr output in this case anyway.
Rather than worrying too much about this yourself, you might want to think about getting HP-UX to do this heavy lifting for you - have a read of the following white paper:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02054623/c02054623.pdf
HTH
Duncan
I am an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2011 11:20 PM
тАО04-12-2011 11:20 PM
Re: scsi queue depth usage
Thanks Duncan for your reply, excellent response. I saw this paper a couple of weeks ago, I'll take time to a have good read of it.
I've came accross a recommendation that the default scsi queue depth of 8 isn't large enough if you have large lun's (500Gb) presented from the eva to the server. I was trying to determine if the scsi queue depth was infact too small.
I guess in the absence of a visable metric I'll have to do some benchmarking with differing queue sizes
Cheers
Michael
I've came accross a recommendation that the default scsi queue depth of 8 isn't large enough if you have large lun's (500Gb) presented from the eva to the server. I was trying to determine if the scsi queue depth was infact too small.
I guess in the absence of a visable metric I'll have to do some benchmarking with differing queue sizes
Cheers
Michael
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP