Vestat

From OpenVZ Virtuozzo Containers Wiki
Revision as of 07:45, 30 May 2008 by Grin (talk | contribs) (let it be)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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/meminfo, as:
    • cpu MHz : frequency_of_your_cpu