All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: ref manual, 2.5, "Speeding Up the Build, " seems a bit confusing
Date: Sat, 10 Jan 2015 08:46:47 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1501100842310.6408@localhost> (raw)


  from that section:

"If you need to achieve even faster builds than what the build system
produces by default, you can consider and implement some of the
following:

  * BB_NUMBER_THREADS, BB_NUMBER_PARSE_THREADS, and PARALLEL_MAKE: As
previously mentioned, the build system scales the values for these
variables. However, you can manually override them in your local.conf
file if you are not satisfied with the defaults."

  but, as i read it from bitbake.conf and bitbake's cooker.py, all
three of those values are already calculated to max out on whatever
dev host is being used:

self.num_processes = int(self.cfgdata.getVar("BB_NUMBER_PARSE_THREADS", True) or
          multiprocessing.cpu_count())

# Default to setting automatically based on cpu count
BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"

# Default to setting automatically based on cpu count
PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"

  so given these dev host-based calculations, how exactly would the
developer manually set them to get even *better* performance? or am i
misreading something?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



                 reply	other threads:[~2015-01-10 13:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.11.1501100842310.6408@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.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.