From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Multi-threaded RPM support
Date: Fri, 02 Jun 2017 16:41:49 -0500 [thread overview]
Message-ID: <1496439709.26945.105.camel@linux.intel.com> (raw)
In-Reply-To: <f71622c0-5f67-999f-da93-b441d1e3445a@linux.intel.com>
Alex,
I get this when bitbake core-image-minimal
http://errors.yoctoproject.org/Errors/Build/38347/
HEAD is at
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/parallel-rpm
On Thu, 2017-06-01 at 20:37 +0300, Alexander Kanavin wrote:
> On 06/01/2017 08:13 PM, Mark Hatle wrote:
> >>> perl
> >>> before: 1m19s 63M
> >>> after: 55s 42M
> >>>
> >>> python3
> >>> before: 40s 38M
> >>> after: 28s 24M
> >>
> >> it is interesting to see that perl and python does not benefit 'much'.
> >> buildstats should give us a better picture per recipe.
> >
> > This may be due to how we process rpmdeps within OpenEmbedded.. but I'm not
> > sure. I'd have expected a bigger time difference with large packages (lots of
> > sub packages) like perl and python3.
>
> The numbers include the overhead of starting bitbake (some 10 seconds).
> Subtract that (from both 'before' and 'after') and then it's more
> impressive :) I tested via
>
> time bitbake -f -c do_package_write_rpm perl
>
> Alex
>
next prev parent reply other threads:[~2017-06-02 21:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:15 [PATCH 0/2] Multi-threaded RPM support Alexander Kanavin
2017-06-01 15:15 ` [PATCH 1/2] package_rpm.bbclass: use multithreaded xz compression Alexander Kanavin
2017-06-01 17:11 ` Mark Hatle
2017-06-01 17:44 ` Alexander Kanavin
2017-06-01 19:02 ` Andre McCurdy
2017-06-02 11:40 ` Alexander Kanavin
2017-06-02 18:33 ` Andre McCurdy
2017-06-01 15:15 ` [PATCH 2/2] rpm: run binary package generation via thread pools Alexander Kanavin
2017-06-01 16:02 ` Alexander Kanavin
2017-06-02 12:44 ` Alexander Kanavin
2017-06-01 16:52 ` [PATCH 0/2] Multi-threaded RPM support Leonardo Sandoval
2017-06-01 17:13 ` Mark Hatle
2017-06-01 17:37 ` Alexander Kanavin
2017-06-02 21:41 ` Leonardo Sandoval [this message]
2017-06-02 22:20 ` Richard Purdie
2017-06-04 14:15 ` Richard Purdie
2017-06-05 12:14 ` Alexander Kanavin
2017-06-05 12:41 ` Alexander Kanavin
2017-06-05 13:01 ` Burton, Ross
2017-06-05 13:15 ` Alexander Kanavin
2017-06-05 13:21 ` Joshua Lock
2017-06-05 13:34 ` Alexander Kanavin
2017-06-05 13:47 ` Davis, Michael
2017-06-05 14:00 ` Alexander Kanavin
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=1496439709.26945.105.camel@linux.intel.com \
--to=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=alexander.kanavin@linux.intel.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