![]() This will determine if the storage is actually a bottleneck, or if the problem is being caused by something else. If a disk performance issue is suspected to be causing a larger problem, we generally start off by running the second set of counters above. However, if you see the counters exceeding the thresholds above, it warrants a deeper investigation. These are general rules and may not apply in every scenario. Queue length isn't directly indicative of performance issues but can help lead to that conclusion. For storage that isn't mapped directly to an array (such as in a private cloud or in Azure), queues should be below 10 or so. For example, if the underlying storage is a 6 disk RAID 5 array, the total disk queue should be 12 or less.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |