15f7be9a52
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
2.0 KiB
vim.StorageResourceManager.StoragePerformanceSummary
Summary statistics for datastore performance The statistics are reported in aggregated quantiles over a time period
- extends
- since
- Attributes:
-
interval (int):
Time period over which statistics are aggregated The reported time unit is in seconds
percentile (int):
Metric percentile specification. A percentile is a value between 1 and 100. The metric value reported in the aggregated statistics corresponds with the percentile values in this field. For example, if the value of percentile[0] is P, and the value of the datastoreReadLatency[0] is L, then P% of all the read IOs performed during observation interval is less than L milliseconds.
datastoreReadLatency (double):
Aggregated datastore latency in milliseconds for read operations
datastoreWriteLatency (double):
Aggregated datastore latency in milliseconds for write operations
datastoreVmLatency (double):
Aggregated datastore latency as observed by Vms using the datastore The reported latency is in milliseconds.
datastoreReadIops (double):
Aggregated datastore Read IO rate (Reads/second)
datastoreWriteIops (double):
Aggregated datastore Write IO rate (Writes/second)
siocActivityDuration (int):
Cumulative SIOC activity to satisfy SIOC latency threshold setting. This metric indicates the total time that SIOC is actively throttling IO requests. The SIOC throttling activity occurs whenever the datastore latency exceeds the SIOC latency threshold. If SIOC is not enabled on the datastore, the metric indicates the total time that SIOC would have been active. The unit of reporting is in milliseconds.