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] rpm: run binary package generation via thread pools
Date: Tue, 13 Jun 2017 11:43:46 -0500 [thread overview]
Message-ID: <1497372226.23013.4.camel@linux.intel.com> (raw)
In-Reply-To: <7f117fed-029a-56e9-b7cd-f342a1f377e6@linux.intel.com>
On Tue, 2017-06-13 at 19:13 +0300, Alexander Kanavin wrote:
>
> Have you ran these all at once? If so, then the wall times aren't very
> meaningful: if the CPU is already saturated by having a lot of bitbake
> tasks running, then adding further threads to these tasks isn't going to
> make anything finish faster than before.
I ran them serially
>
>
> Alex
>
prev parent reply other threads:[~2017-06-13 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 14:58 [PATCH] rpm: run binary package generation via thread pools Alexander Kanavin
2017-06-12 15:01 ` ✗ patchtest: failure for " Patchwork
2017-06-12 15:02 ` [PATCH] " Alexander Kanavin
2017-06-12 19:29 ` Leonardo Sandoval
2017-06-13 16:15 ` Leonardo Sandoval
2017-06-13 16:13 ` Alexander Kanavin
2017-06-13 16:43 ` Leonardo Sandoval [this message]
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=1497372226.23013.4.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 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.