All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: linux-yocto task performance numbers
Date: Mon, 23 Feb 2015 10:22:04 +0000	[thread overview]
Message-ID: <1424686924.11836.78.camel@linuxfoundation.org> (raw)
In-Reply-To: <1424686123.11836.76.camel@linuxfoundation.org>

Also, for reference/interest, the recent kernel populate_sysroot changes
took the kernel build time from over 11 mins to 8 mins. With the move to
3.19:

fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 7:58.74
fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 7:57.59
fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 7:59.18
fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 8:00.81
fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 8:01.44
fedora19,master:5db6a27f4847e51c6434a968f81d3ceffcc54952 7:59.12
fedora19,master:172606338757d0b788e3382bf413102647307e1d 8:29.71
fedora19,master:172606338757d0b788e3382bf413102647307e1d 8:37.66
fedora19,master:172606338757d0b788e3382bf413102647307e1d 8:36.41
fedora19,master:172606338757d0b788e3382bf413102647307e1d 8:34.24
fedora19,master:172606338757d0b788e3382bf413102647307e1d 8:36.19

You can see 3.19 takes around 30-35s longer to build. These numbers are
extracted from our benchmark machine which monitors things like this.

Cheers,

Richard



  reply	other threads:[~2015-02-23 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-22 13:04 linux-yocto task performance numbers Richard Purdie
2015-02-22 14:05 ` Bruce Ashfield
2015-02-23  5:13 ` Bruce Ashfield
2015-02-23 10:08   ` Richard Purdie
2015-02-23 10:22     ` Richard Purdie [this message]
2015-02-23 13:14     ` Bruce Ashfield
2015-02-23 16:25 ` Hart, Darren

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=1424686924.11836.78.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=darren.hart@intel.com \
    --cc=openembedded-core@lists.openembedded.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.