Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] sstatetests: Use higher parallelism value
Date: Wed, 14 Jun 2017 11:54:50 +0100	[thread overview]
Message-ID: <1497437690.3942.46.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=UvrqetBfC0_RgJJbiOUYzEatksZb7txh4H5d7RFaoeKQ@mail.gmail.com>

On Tue, 2017-06-13 at 08:55 -0700, Andre McCurdy wrote:
> On Tue, Jun 13, 2017 at 2:49 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 
> > Since the processing code for signature generation is now threaded,
> > use higher thread values as examples in this code for better
> > performance.
> > 
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > ---
> >  meta/lib/oeqa/selftest/cases/sstatetests.py | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/meta/lib/oeqa/selftest/cases/sstatetests.py
> > b/meta/lib/oeqa/selftest/cases/sstatetests.py
> > index 8d05e30..feadf3c 100644
> > --- a/meta/lib/oeqa/selftest/cases/sstatetests.py
> > +++ b/meta/lib/oeqa/selftest/cases/sstatetests.py
> > @@ -418,7 +418,7 @@ DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
> > 
> >          self.write_config("""
> >  TMPDIR = "${TOPDIR}/tmp-sstatesamehash"
> > -BB_NUMBER_THREADS = "1"
> > +BB_NUMBER_THREADS = "${@oe.utils.cpu_count()}"
> >  PARALLEL_MAKE = "-j 1"
> >  DL_DIR = "${TOPDIR}/download1"
> >  TIME = "111111"
> > @@ -431,7 +431,7 @@ http_proxy = ""
> >          bitbake("world meta-toolchain -S none")
> >          self.write_config("""
> >  TMPDIR = "${TOPDIR}/tmp-sstatesamehash2"
> > -BB_NUMBER_THREADS = "2"
> > +BB_NUMBER_THREADS = "${@oe.utils.cpu_count()-1}"
> What happens here if I have one CPU core?

I'll change it to a +1 :)

Cheers,

Richard


  reply	other threads:[~2017-06-14 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  9:49 [PATCH 1/5] allarch: Append to vardepsexclude, not overwrite Richard Purdie
2017-06-13  9:49 ` [PATCH 2/5] insane: Don't depend on OVERRIDES Richard Purdie
2017-06-13  9:49 ` [PATCH 3/5] utils: Exclude OVERRIDES from hashes in multilib functions Richard Purdie
2017-06-13  9:49 ` [PATCH 4/5] sstatetests: Use higher parallelism value Richard Purdie
2017-06-13 15:55   ` Andre McCurdy
2017-06-14 10:54     ` Richard Purdie [this message]
2017-06-13  9:49 ` [PATCH 5/5] bitbake.conf: Don't exclude MACHINE/MACHINEOVERRIDES from hashes Richard Purdie
2017-06-13 10:01 ` ✗ patchtest: failure for "allarch: Append to vardepsexcl..." and 4 more Patchwork

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=1497437690.3942.46.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.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