- vSphere High Performance Cookbook(Second Edition)
- Kevin Elder Christopher Kusek Prasenjit Sarkar
- 154字
- 2021-07-02 20:59:52
How it works…
Although high ready time typically signifies CPU contention, the condition does not always warrant corrective action. If the value of ready time is also accompanied by high used time, then it might signify that the host is overcommitted.
So the used time and ready time of a host might signal contention. However, the host might not be overcommitted due to workload availability.
There might be periods of activity and periods that are idle. So the CPU is not over-committed all the time. Another very common source of high ready time for VMs, even when pCPU utilization is low, is due to storage being slow. A vCPU, which occupies a pCPU, can issue a storage I/O and then sit in the WAIT state on the pCPU, blocking other vCPUs. Other vCPUs accumulate ready time; this vCPU and pCPU accumulate wait time (which is not part of the used or utilized time).
- Django+Vue.js商城項目實戰
- Spring 5企業級開發實戰
- Hyper-V 2016 Best Practices
- Rust編程:入門、實戰與進階
- Python 深度學習
- Learning C++ Functional Programming
- Reactive Programming with Swift
- Animate CC二維動畫設計與制作(微課版)
- Cassandra Data Modeling and Analysis
- Spring實戰(第5版)
- Extending Puppet(Second Edition)
- C語言從入門到精通
- Julia High Performance(Second Edition)
- Java程序設計入門(第2版)
- 網絡綜合布線與組網實戰指南