BMC-CLM CLOUD LIFE CYCLE MANAGEMENT AN OVERVIEW: BMC Cloud Lifecycle Management brings together the benefits of traditional IT management, including operational excellence, automation, and service delivery models, and merges them with the dynamic potential of cloud architectures. It provides the foundation for a strong, flexible, and valuable cloud infrastructure that supports IT operations and delivers exceptional service quality to the business. FEATURES AND FUNICTIONALITY OF BMC CLOUD LIFE CYCLE: Support for different cloud infrastructure options: Citrix XenServer, VMware vSphere, VMware vCloud Director, Openstack, IBM pSeries, Microsoft Hyper-V, Amazon Web Services, Savvis, Terremark etc. Support for different guest operating systems on virtual and physical systems: Redhat Linux, Microsoft Windows 2008 and 2012, IBM AIX, SUSE Linux Enterprise Server, Oracle Enterprise Linux Self-service portal for business users: deliver complete, configurable services without IT intervention ...

What is Queue depth? It is the number of I/O operations that can run in parallel on a LUN/blocks. Generally, it specifies the number of outstanding requests per LUN. It is the number of I/O requests that the initiator can send and receive per LUN. Each I/O request from the host’s initiator HBA to the storage target adapter ingests a queue entry. Typically, a higher queue depth equates to improved performance. However, if the storage controller’s maximum queue depth is reached, that storage controller discards incoming I/O request by returning queue full response to the initiator, causing bottlenecks and latency issues. The following general recommendations can be made about "tuning" queue depths. For small to mid-size systems, use a HBA queue depth of 32. For large systems, use a HBA queue depth of 128. For exception cases or performance testing, use a queue depth of 256 to avoid possible queuing problems. All hosts should have the queue d...