All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: compute performace problem
Date: Sat, 23 Apr 2005 16:14:39 +0100	[thread overview]
Message-ID: <7b76dbdaf72a4bda7a124b671dd30293@cl.cam.ac.uk> (raw)
In-Reply-To: <E1DPMDS-0007al-00@mta1.cl.cam.ac.uk>


On 23 Apr 2005, at 16:06, Steven Hand wrote:

>> One of my users discovered large deviations in execution time for his
>> mpi jobs on xenUs.  I can reproduce the problem running his job on
>> a single VM.  On a native linux box the job completes in 64 secs +/-
>> a second or so.  On a xenU, it completes somewhere between 64 and 250
>> secs.  This is true on 2.0.5 (2.6.10-xenU) and 
>> 2.0-testing(2.6.11-xenU).
>> I tried xen-unstable but it seemed any task was taking 4 times as
>> long as on 2.0 so I guess its still too unstable.
>>
>> Any suggestions I can try?
>
> Can you repeat the experiment using the round robin scheduler in Xen 
> (i.e.
> boot with xen option "sched=rrobin")?

Probably will be worse -- I'm not certain that the rrobin scheduler is 
even smart enough not to include the idle domain in its round-robin 
schedule. An important reason why I killed it in the unstable tree.

  -- Keir

  reply	other threads:[~2005-04-23 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-23 14:52 compute performace problem David Becker
2005-04-23 15:06 ` Steven Hand
2005-04-23 15:14   ` Keir Fraser [this message]
2005-04-23 15:12 ` Keir Fraser
2005-04-23 16:50   ` David Becker
2005-04-23 17:53     ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-04-23 21:17 Ian Pratt
2005-04-24 17:28 ` David Becker
2005-04-24 17:54   ` Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7b76dbdaf72a4bda7a124b671dd30293@cl.cam.ac.uk \
    --to=keir.fraser@cl.cam.ac.uk \
    --cc=Steven.Hand@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.