From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Buildhistory in action
Date: Thu, 19 Jan 2012 14:45:29 +0000 [thread overview]
Message-ID: <12179414.hR7YIgmyms@helios> (raw)
In-Reply-To: <7BD299FF-ED9A-4C3C-9581-4EF9B8D89B25@dominion.thruhere.net>
On Thursday 19 January 2012 15:37:38 Koen Kooi wrote:
> If you want to see a longer history, have a look at
> https://github.com/Angstrom-distribution/buildhistory/commits/master, I've
> been using it heavily today when working on udev 177 which changed its
> default filesystem layout. One thing to keep in mind:
>
> $ du -hs /data/ssd/OE/buildhistory/
> 548M /data/ssd/OE/buildhistory/
Hmm, I wouldn't have expected it to be quite that large, but I guess it
depends what you're doing with it, and I'd imagine given the number of builds
you run you probably stress it more than most (which is good :). In the end
500M is just a drop in the bucket compared to the rest of TMPDIR...
> I keep it on an SSD to avoid needing to wait a few minutes after every
> bitbake invocation.
Good advice :) It's also worth noting it will noticeably increase the
do_rootfs time (especially for RPM) and probably do_package as well.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-19 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:08 Buildhistory in action Richard Purdie
2012-01-19 14:37 ` Koen Kooi
2012-01-19 14:45 ` Paul Eggleton [this message]
2012-01-19 14:59 ` Koen Kooi
2012-01-19 15:04 ` Paul Eggleton
2012-01-19 16:06 ` Mark Hatle
2012-01-19 16:22 ` Paul Eggleton
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=12179414.hR7YIgmyms@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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.