From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Cc: Meng Xu <mengxu@cis.upenn.edu>
Subject: Re: [PATCH OSSTEST] ts-debian-install: increase time allowed for xen-create-image
Date: Fri, 15 Jan 2016 15:44:44 +0100 [thread overview]
Message-ID: <1452869084.11427.68.camel@citrix.com> (raw)
In-Reply-To: <1452864930-5901-1-git-send-email-ian.campbell@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2074 bytes --]
On Fri, 2016-01-15 at 13:35 +0000, Ian Campbell wrote:
> This step is consistently timing out when run on cubietruck-*.
> Judging
> from the logs it appears to be completing during the 30s slack added
> by tcmdex (i.e. after the timeout message the rest of the output
> appears in the test step log).
>
> Looking at the results on arndale-* (which looks to pass reasonably
> reliably) I see that the regular test-armhf-armhf-xl job takes around
> 550s to do the xen-create-image while test-armhf-armhf-xl-rtds
> typically takes around 1100s (twice as long).
>
> On cubietruck-braque test-armhf-armhf-xl uses 900s. One could
> therefore extrapolate that test-armhf-armhf-xl-rtds might need more
> than 1800s and not be too surprised that it appears to need something
> a bit more than 2000s in practice. 2500s seems like sufficient
> headroom.
>
> For comparisson with arm on x86 godello takes around 210s in the
> normal case and 680s with RTDS (>3x slower) while nocera takes 265s
> and 640s (2.4x). (Those are from nearby but not identical flights in
> order to match up the host).
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
> ---
> Dario, Meng, I suppose a 2-3x slow down with RTDS on a dom0 operation
> (with no domains running) such as xen-create-image is not unexpected?
>
Yes, as of now, I think it is. RTDS' default scheduling parameters
throttle domains' vcpus to max 40% of CPU, non work conserving mode
(i.e.m, they only consume up to that much even if there is idle time).
I think this will have to change at some point, but for now, slowdowns
for operation like the ones in xen-create-image are to be expected, and
this patch looks therefore ok to me.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-15 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 13:35 [PATCH OSSTEST] ts-debian-install: increase time allowed for xen-create-image Ian Campbell
2016-01-15 14:44 ` Dario Faggioli [this message]
2016-01-15 14:57 ` Ian Campbell
2016-01-15 16:39 ` Ian Jackson
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=1452869084.11427.68.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=mengxu@cis.upenn.edu \
--cc=xen-devel@lists.xen.org \
/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.