Connectivity-Aware Storage Controller Load Balancing
US-2015293708-A1 · Oct 15, 2015 · US
US10552287B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10552287-B2 |
| Application number | US-201815981745-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 16, 2018 |
| Priority date | Apr 15, 2014 |
| Publication date | Feb 4, 2020 |
| Grant date | Feb 4, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
The disclosed embodiments include a method for identifying a performance metric to diagnose a cause of a performance issues of virtual machine. The method includes obtaining data of a virtual machine, an indication that a storage volume contains data of the virtual machine, data about the storage volume, and an identification of the storage volume. The data of the virtual machine is correlated with the data about the storage volume based on the indication that the storage volume contains data of the virtual machine and the identification of the storage volume. A performance metric is identified based at least in part on an outcome of the correlating. The performance metric indicates that the storage volume is a cause of a performance issue of the virtual machine. A state related to the storage volume is changed to mitigate the cause of the performance issue of the virtual machine.
Opening claim text (preview).
The invention claimed is: 1. A method comprising: obtaining data of a virtual machine and an indication that a storage volume contains data of the virtual machine; obtaining data related to the storage volume and an identification of the storage volume; correlating the data of the virtual machine with the data related to the storage volume by (a) determining that the data of the virtual machine data identifies the storage volume, and (b) determining that the data related to the storage volume identifies the storage volume; identifying a performance metric based at least in part on an outcome of the correlating, the performance metric being indicative that the storage volume is a cause of a performance issue of the virtual machine; and causing a change in a state related to the storage volume to mitigate the cause of the performance issue of the virtual machine. 2. The method of claim 1 further comprising: causing display to a user of performance information including the identified performance metric, the performance information including the indication that the storage volume is the cause of the performance issue of the virtual machine. 3. The method of claim 1 , wherein the performance metric is a CPU performance metric based on at least one of a maximum CPU usage, an average CPU usage of the virtual machine, or a state waiting for CPU time of the virtual machine. 4. The method of claim 1 , wherein the performance metric is a memory performance metric based on at least one of a maximum memory usage, a ballooned memory, a swapped memory, or an average memory usage. 5. The method of claim 1 , wherein the performance metric is based on a total amount of memory that is reclaimed from a plurality of virtual machines on a host of the virtual machine. 6. The method of claim 1 , wherein the performance metric is based on a total amount of memory swapped among virtual machines on a host of the virtual machine. 7. The method of claim 1 , further comprising: changing a state of the performance metric based on a remaining storage space in a data store. 8. The method of claim 1 , further comprising: changing a state of the performance metric based on an amount of storage space of the storage volume that is over-provisioned. 9. The method of claim 1 , wherein the performance metric is based on memory that is actively in use in the virtual machine. 10. The method of claim 1 , wherein the performance metric is based on a virtual memory saved by memory sharing. 11. The method of claim 1 , wherein the performance metric is based on a virtual memory used to power the virtual machine. 12. The method of claim 1 , wherein the performance metric is based on physical memory that is mapped to the virtual machine, which precludes overhead memory. 13. The method of claim 1 , wherein the performance metric is based on an amount of physical memory that is reclaimed by a host of the virtual machine through a ballooning driver. 14. The method of claim 1 , wherein the performance metric is based on memory that is read by the virtual machine from a swap file of a host of the virtual machine. 15. The method of claim 1 , wherein the performance metric is based on an amount of memory that the virtual machine has had to write to a swap file. 16. The method of claim 1 , wherein the performance metric is based on an amount of memory of the virtual machine that has been swapped by a host of the virtual machine. 17. The method of claim 1 , wherein the performance metric is indicative of any of a task assignment count, a task assignment type, or a task completion count, or describes migrations between the virtual machine or a host of the virtual machine. 18. The method of claim 1 further comprising: causing generation of a visualization of the performance metric indicating that the storage volume is a cause of a performance issue of the virtual machine. 19. The method of claim 1 , wherein the performance metric describes a property of a virtual environment including the virtual machine, a host of the virtual machine, a virtual machine manager, and a virtual system manager. 20. The method of claim 1 further comprising: causing generation of a visualization of the performance metric in a graphical interface that enables a user to visually determine the cause of the performance issue of the virtual machine. 21. The method of claim 1 further comprising: causing generation of a visualization of a value associated with the performance metric in a graphical interface, the visualization being indicative of the cause of the performance issue of the virtual machine. 22. The method of claim 1 , wherein the performance metric is a type of computer cluster performance metric. 23. The method of claim 1 , wherein the performance metric is a host-based replication performance metric. 24. The method of claim 1 , wherein the performance metric is a memory performance metric. 25. The method of claim 1 , wherein the performance metric is a network performance metrics. 26. The method of claim 1 , wherein the performance metric is a power performance metric. 27. The method of claim 1 , wherein the performance metric is a debug performance metric. 28. The method of claim 1 , wherein the performance metric is a resource performance metric. 29. An apparatus comprising: a processor; and a memory having instructions executable by the processor to cause the system to: obtain data of a virtual machine and an indication that a storage volume contains data of the virtual machine; obtain data related to the storage volume and an identification of the storage volume; correlate the data of the virtual machine with the data related to the storage volume by (a) determining that the data of the virtual machine data identifies the storage volume, and (b) determining that the data related to the storage volume identifies the storage volume; identify a performance metric based at least in part on an outcome of the correlating, the performance metric being indicative that the storage volume is a cause of a performance issue of the virtual machine; and causing a change in a state related to the storage volume to mitigate the cause of the performance issue of the virtual machine. 30. One or more non-transitory storage media storing instructions that, when executed by one or more computing devices, cause: obtaining data of a virtual machine and an indication that a storage volume contains data of the virtual machine; obtaining data related to the storage volume and an identification of the storage volume; correlating the data of the virtual machine with the data related to the storage volume by (a) determining that the data of the virtual machine data identifies the storage volume, and (b) determining that the data related to the storage volume identifies the storage volume; identifying a performance metric based at least in part on an outcome of the correlating, the performance metric being indicative that the storage volume is a cause of a performance issue of the virtual machine; and causing a change in a state related to the storage volume to mitigate the cause of the performance issue of the virtual machine. 31. The method of claim 1 , further comprising: causing display of a user interface that includes information identifying the virt
where the computing system is a virtual computing platform, e.g. logically partitioned systems (virtual machines G06F9/45533; logical partitioning of resources G06F9/5077) · CPC title
for performance assessment · CPC title
Monitoring arrangements determined by the means or processing involved in reporting the monitored data (error or fault reporting or logging G06F11/0766) · CPC title
where the computing system component is a storage system, e.g. DASD based or network based (digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097) · CPC title
I/O management, e.g. providing access to device drivers or storage · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.