All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: FW: [oe] BitBake parallel parsing testing
Date: Wed, 24 Nov 2010 10:30:29 +0000	[thread overview]
Message-ID: <1290594629.2799.0.camel@scimitar> (raw)
In-Reply-To: <4CECE001.6050201@mlbassoc.com>

On Wed, 2010-11-24 at 02:50 -0700, Gary Thomas wrote:
> On 11/24/2010 01:45 AM, Xu, Dongxiao wrote:
> > FYI, bitbake parallel parsing is enabled, which can greatly reduce the file parsing time.
> > There are some data test result in OE's following mails.
> >
> > Bitbake 1.10: 3m2.185s
> > parallel-parsing (BB_NUM_PARSE_THREADS=num_cpu): 1m48.232s parallel-parsing (BB_NUM_PARSE_THREADS=2*num_cpu): 1m1.869s
> 
> To be clear - this is in the Poky main tree?  since what commit?

No, this is an RFC from one of the bitbake developers and currently only
resides in his personal branch of bitbake.

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



  reply	other threads:[~2010-11-24 10:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24  8:45 FW: [oe] BitBake parallel parsing testing Xu, Dongxiao
2010-11-24  9:50 ` Gary Thomas
2010-11-24 10:30   ` Joshua Lock [this message]
2010-11-24 10:40 ` Tian, Kevin

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=1290594629.2799.0.camel@scimitar \
    --to=josh@linux.intel.com \
    --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.