public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] package_manager.py: fix rpm based do_rootfs failed while IMAGE_INSTALL_append = " python3"
Date: Mon, 16 Feb 2015 10:01:22 +0000	[thread overview]
Message-ID: <1424080882.25541.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <54DD55E2.6090709@windriver.com>

On Fri, 2015-02-13 at 09:39 +0800, Hongxu Jia wrote:
> On 02/13/2015 12:46 AM, Paul Eggleton wrote:
> >> default_archs) +                new_pkg =
> >> >self._search_pkg_name_in_feeds(pkg, default_archs) or \ +
> >> >  self._search_pkg_provider_in_smart(pkg, default_archs) if not new_pkg:
> >> >                      err_msg = '%s not found in the base feeds (%s).\n' % \
> >> >                                (pkg, ' '.join(default_archs))
> > It took a long time to reply to this, my apologies. This patch looks OK but
> > Richard pointed out that it may have an impact on the speed of do_rootfs
> > because of the extra calls out to smart. Do you have any performance impact
> > figures?
> 
> Hi Paul,
> 
> The extra 'smart' calling takes 3-5 seconds for one search,
> but it will not do that for most packages, it goes into
> self._search_pkg_name_in_feeds first, if not found and then in to
> self._search_pkg_provider_in_smart, only if we have such as python3
> in the build session, it will take extra 3-5 seconds.

Could we test the time it takes to build core-image-sato-sdk before and
after this patch please?

Cheers,

Richard



  reply	other threads:[~2015-02-16 10:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31  9:46 [PATCH V2 0/1] package_manager.py: fix rpm based do_rootfs failed while IMAGE_INSTALL_append = " python3" Hongxu Jia
2014-10-31  9:46 ` [PATCH 1/1] " Hongxu Jia
2015-02-12 16:46   ` Paul Eggleton
2015-02-13  1:39     ` Hongxu Jia
2015-02-16 10:01       ` Richard Purdie [this message]
2014-12-11  7:42 ` [PATCH V2 0/1] " Hongxu Jia
2014-12-22  1:55 ` Hongxu Jia
2015-01-08  8:55 ` Hongxu Jia
  -- strict thread matches above, loose matches on Subject: below --
2014-10-31  7:05 [PATCH " Hongxu Jia
2014-10-31  7:05 ` [PATCH 1/1] " Hongxu Jia
2014-10-31  8:50   ` Laurentiu Palcu
2014-10-31  9:30     ` Hongxu Jia

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=1424080882.25541.0.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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