All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
	openembedded-core@lists.openembedded.org,
	Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
Subject: Re: [PATCH 0/2] Multi-threaded RPM support
Date: Thu, 1 Jun 2017 20:37:41 +0300	[thread overview]
Message-ID: <f71622c0-5f67-999f-da93-b441d1e3445a@linux.intel.com> (raw)
In-Reply-To: <b191e2fc-65c7-350f-1a7e-da684ca6b2b5@windriver.com>

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



  reply	other threads:[~2017-06-01 17:39 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 [this message]
2017-06-02 21:41       ` Leonardo Sandoval
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=f71622c0-5f67-999f-da93-b441d1e3445a@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=mark.hatle@windriver.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 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.