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-users

Re: [Xen-users] Re: Xen Scheduler: Credit Scheduler ?

To: Emmanuel Ackaouy <ack@xxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: Xen Scheduler: Credit Scheduler ?
From: "Ulrich Windl" <ulrich.windl@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 24 Nov 2006 08:23:54 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 23 Nov 2006 23:24:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20061123113350.GA26604@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Universitaet Regensburg, Klinikum
Priority: normal
References: <C34CDA8AB8DD244D9981101A6AD7EC940728BD76@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 23 Nov 2006 at 11:33, Emmanuel Ackaouy wrote:

> It's a bit frustrating that we're not making progess isolating
> the problem here.
> 
> We still don't have any concrete evidence showing that the
> benchmark user processes or domain VCPU are or aren't runnable
> when you notice the "stall".

Stupid idea: just write a program that outputs the time of day at high 
resolution 
to some file. The run at least one such program in each domain (preferrably 
with 
synced clocks), then inspect the output for discontinuities.

> 
> It's also not clear what is the simplest scenario under which
> the problem can be reproduced. I tried reading your explanation
> about what happens with UP guests but I can't understand it.
> Can you clarify exactly what you are doing and in what order?

If it's not CPU-bound (the example uses little I/O), you could try something 
like 
copying as much data as 90% of your RAM from one file to another. Logically if 
a 
process in Dom0 is blocked on I/O, the scheduler can do little to help DomUs 
waiting for completion of that I/O. I suspect...

> 
> I threw around some ideas to get more data points and help
> debug this:
> - run spinners on the guest that consume CPU
>     "int main() { while (1); return 0; }" and run X copies (for X vcpus)
> - take scheduler traces (man xentrace)

A bad example, because that will either be optimized that it will execute in 
CPU's 
L1 cache, thus causing about no load at all (assuming a SMP system).

What about "find /usr -type f | xargs cat | gzip >/dev/null" instead. If you 
have 
plenty of room output to some real file. That's some load.

Regards,
Ulrich


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users