From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] can one identify how much work sstate cache would save a build?
Date: Sun, 12 Sep 2021 16:54:31 +0100 [thread overview]
Message-ID: <7af69960b5cc22aa021b1814c883a3ac8ff8c592.camel@linuxfoundation.org> (raw)
In-Reply-To: <9c5322ee-8fcb-180-133d-d96610f31440@crashcourse.ca>
On Sun, 2021-09-12 at 10:00 -0400, Robert P. J. Day wrote:
> off the wall question from a friend, but is there a way to get a
> general idea of how much work (how many tasks?) could be saved for a
> build based on some available sstate cache directory?
Run a build with bitbake -n against it and there is a summary printed near the
start of the build which says something like:
Sstate summary: Wanted 1525 Local 0 Network 1515 Missed 10 Current 0 (99% match, 0% complete)
Cheers,
Richard
next prev parent reply other threads:[~2021-09-12 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 14:00 can one identify how much work sstate cache would save a build? Robert P. J. Day
2021-09-12 15:54 ` Richard Purdie [this message]
2021-09-12 15:59 ` [OE-core] " Robert P. J. Day
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=7af69960b5cc22aa021b1814c883a3ac8ff8c592.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.