From: Martin Jansa <martin.jansa@gmail.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: Re: rm_work + pybootchart enhancements
Date: Wed, 21 Sep 2016 18:08:54 +0200 [thread overview]
Message-ID: <20160921160854.GB2633@jama> (raw)
In-Reply-To: <1474472342.16834.96.camel@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
On Wed, Sep 21, 2016 at 05:39:02PM +0200, Patrick Ohly wrote:
> Hello!
>
> rm_work.bbclass currently isn't good enough for use in really tightly
> constrained environments. For example, building core-image-sato with
> 20GB of free disk space should work (final disk usage with rm_work
> active: <13GB). But in practice, that disk space gets exhausted in the
> middle of a build because do_rm_work doesn't run often and/or soon
> enough.
I agree that it could use some improvements, but I'm using simple work
around for this - building whole image in couple steps which forces
rm_work being executed often enough to fit WORKDIR in e.g. 14G tmpfs
something like:
bitbake gcc && bitbake console-image && bitbake webkit && bitbake bigger-image
> Test script attached. I only ran this once, so I can't vouch that the
> numbers are stable. I remember reading about a benchmark wrapper which
> can run such a test script multiple times and then will automatically
> merge the output of all runs together, adding min/max/average/deviation,
> but couldn't find the tool again. Does anyone know which tool does that?
it's in oe-core:
./scripts/contrib/bb-perf/bb-matrix-plot.sh
./scripts/contrib/bb-perf/bb-matrix.sh
...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
next prev parent reply other threads:[~2016-09-21 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 15:39 rm_work + pybootchart enhancements Patrick Ohly
2016-09-21 16:08 ` Martin Jansa [this message]
2016-09-22 12:52 ` Patrick Ohly
2016-09-22 17:37 ` Christopher Larson
2016-09-23 5:51 ` Patrick Ohly
2016-09-23 6:01 ` Patrick Ohly
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=20160921160854.GB2633@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox