Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Build Times and Performance - Discussion + new ideas
Date: Fri, 30 Sep 2011 11:12:18 +0100	[thread overview]
Message-ID: <1317377605.12332.140.camel@ted> (raw)
In-Reply-To: <CAEsOVNc1Ckw-eCFSTGLngecojM=gR5rvphLFKP5TRfn17pobcg@mail.gmail.com>

On Fri, 2011-09-30 at 01:11 +0000, McClintock Matthew-B29882 wrote:
> On Tue, Sep 27, 2011 at 12:07 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > https://wiki.yoctoproject.org/wiki/Build_Performance
> >
> > As detailed there I've setup a partition formatted with ext4 with no
> > journal, no barriers and most importantly a long commit time. The intent
> > here is to allow things to exist in memory and not block on disk IO.
> 
> Can you comment on how much these settings effect build times vs.
> saying running on ext3 which our build server happens to be using?

I don't have absolute numbers but there are the following performance
limiting factors:

- journal - turned off means faster but more data risk
- ext4 has extents (which if nothing else allow deletion of build 
  directories faster). I suspect these are a big win for us given how 
  much direct file writing we do during unpack
- noatime changes - reduces amount of writes needed
- commit time changes - not forced to only keep 5 seconds of data in 
  memory maximum so less process blocking on IO.

You can do some of these things on ext3 (or just enable the features on
your existing ext3 disk and start using them, you don't need to
reformat).

If the disk is your system and build disk, I'd get more worried and
probably not recommend the changes. I'd recommend a separate build disk
where at all possible.

Cheers,

Richard




  reply	other threads:[~2011-09-30 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 17:07 Build Times and Performance - Discussion + new ideas Richard Purdie
2011-09-30  1:11 ` McClintock Matthew-B29882
2011-09-30 10:12   ` Richard Purdie [this message]
2011-09-30 12:44 ` Richard Purdie

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=1317377605.12332.140.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox