Editing Vestat
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 6: | Line 6: | ||
* '''VEID''': The VE ID, obviously. | * '''VEID''': The VE ID, obviously. | ||
* '''user, nice, system, uptime''': usage in [[jiffy|jiffies]]. These are the equivalents of <code>/proc/stat</code>, but there is no ''idle'' because it cannot be measured this way. | * '''user, nice, system, uptime''': usage in [[jiffy|jiffies]]. These are the equivalents of <code>/proc/stat</code>, but there is no ''idle'' because it cannot be measured this way. | ||
| − | * '''idle, strv, uptime, used''': usage in [[cycle|cycles]]. | + | * '''idle, strv, uptime, used''': usage in [[cycle|cycles]]. idle and uptime are obvious, strv isn't used, and used is the used cycles by VE on all CPUs. |
| − | * '''maxlat, totlat, numsched''': latency statistics in cycles | + | * '''maxlat, totlat, numsched''': latency statistics in ''cycles''. maxlat is max latency in cycles meaning how long VE process has to wait before it actually got CPU time; totlat/numsched gives average scheduling latency. '''These do not seem work in OpenVZ, only in Virtuozzo.''' |
== Measure conversions == | == Measure conversions == | ||
