OpenVZ Forum


Home » General » Support » Questions about vestat measures interpretation
Questions about vestat measures interpretation [message #36202] Thu, 28 May 2009 14:12
Atosboy is currently offline  Atosboy
Messages: 15
Registered: April 2009
Junior Member
Hi,

We are tyring to analyze the CPU activity of our VPSes by executing a bunch of tests.
To do so:
  • the CPU states (user, system, idle...) of each VPS are captured every 5 seconds with a "cat" of the /proc/vz/vestat file;
  • the CPU activity of the host is captured every 5 seconds too but with a "cat" of the /proc/stat file (since vestat does not provide any information about the host, a.k.a. "VPS 0");


We've got the following questions:
1) We found that the 'idle' duration is constant and is about 5 sec. (this has been checked in a test which produces 1200 snapshots...): the 'idle' duration is constant even when the 'user' activity increases strongly.

Since the CPU snapshots are taken every 5 seconds and the processor of our platform is a dual core, we were initially expecting the sum of durations (user+nice+system+idle) to be comprised between 5 and 10 seconds. However, the sum is sometimes far higher because the 'idle' duration never changes.

4) We are wondering if a simple relation exists between the host CPU consumption and the VPSes CPU consumption?
We observe that when the CPU activity of one or more VPSses increases, the host CPU activity increases too, and conversely.
But we do not understand why the host CPU consumption is:
  • not equal to the sum of all VPSes CPU consumptions;
  • sometimes, the host CPU consumption (indicated by /proc/stat) is lower than the CPU consumption of one VPS (returned by /proc/vz/vestat)...


Thank you in advance,

Fred

This analyze has been made with:

[Updated on: Mon, 01 June 2009 12:09]

Report message to a moderator

 
Read Message
Previous Topic: VMWare on same host as OpenVZ
Next Topic: Upgrade Guest from CentOS 4.7 to 5.3
Goto Forum:
  


Current Time: Sun Aug 18 07:24:48 GMT 2024

Total time taken to generate the page: 0.02882 seconds