Difference between revisions of "Vestat"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
m (fix tipography a bit)
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 and uptime are obvious, strv isn't used, and used is the used cycles by VE on all CPUs.
+
* '''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 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.'''
+
* '''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 ==

Revision as of 12:39, 23 March 2009

The /proc/vz/vestat file contains statistics for VE CPU usage.

The guessed content (may the Gods - blessed thy fingers - acknowledge or reject my humble info here):

  • VEID: The VE ID, obviously.
  • user, nice, system, uptime: usage in jiffies. These are the equivalents of /proc/stat, but there is no idle because it cannot be measured this way.
  • idle, strv, uptime, used: usage in 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 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

Using jiffies:

  • seconds = measurement / jiffies_per_seconds

Using cycles:

  • seconds = measurement / cycles_per_jiffy / jiffies_per_seconds.

Variables:

  • jiffies_per_second = 1000 (unless you have changed that in kernel config?)
  • cycles_per_jiffy = frequency_of_your_cpu / jiffies_per_second
  • frequency_of_your_cpu (in Hz) can be read from /proc/cpuinfo, as:
    • cpu MHz : frequency_of_your_cpu