WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

Re: [Xen-API] Strange CPU utilization values of Dom0

To: kushalwaikar@xxxxxxxxxxx
Subject: Re: [Xen-API] Strange CPU utilization values of Dom0
From: Stefan de Konink <stefan@xxxxxxxxx>
Date: Thu, 26 Feb 2009 02:10:39 +0100
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 25 Feb 2009 17:10:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <626887.1479.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <626887.1479.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20081209)
kushal waikar wrote:
    >take two values you measure, substract them and divide them by the actual 
time
    >in milliseconds that has passed between measuring.

    >This will give you a value that corresponds with the load.


    1st value(Say 'V1') : 0.316815906659 ( Unit = ? )
    2nd value(Say 'V2') : 0.344911681094 ( Unit = ? )
    1st value - 2nd value = V1-V2 = 0.028095774435 ( Unit = ? )

    actual time in milliseconds that has passed between measuring(say 't'): 
1sec = 1000 milliseconds

    therefore final answer = (V1-V2)/t = 0.000028095774435  ( Unit = ? )

    Please correct me wherever I am going wrong in computation...

Where did you pass your highschool? V1 - V2 != V2 - V1 interesting enough you absolute your value but you do not denote this.

The value itself might be already in seconds; so in that case it is divided by one. and 0.03 makes sense as cpu load.


Stefan

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api