From: Robert Yang <liezhi.yang@windriver.com>
To: <yocto@yoctoproject.org>, <paul.eggleton@linux.intel.com>
Subject: [layerindex-web][PATCH 0/5] update.py: performance improve and 2 fixes
Date: Wed, 3 Jan 2018 13:42:21 +0800 [thread overview]
Message-ID: <cover.1514957220.git.liezhi.yang@windriver.com> (raw)
Hi Paul,
This email contains two parts:
- The first 2 are bug fixes
- The other 3 are performance improvements, I have 124 layers,
the "update.py -b <branch>" needs about 9m20s to finish the running when everything is
update, and we have several branches, we need them to run in periodically
(e.g., per 30 mins, the short the better), so one branch 9m20s is really a problem.
Only about 1m43s are needed with these improvements when set PARALLEL_JOBS to 10:
update.py: fetch repos parallelly # Saved 2 mins
update_layer.py: use it as a module # Saved 5 mins
update_layer.py: only call init_parser when needed # Saved 1 min
// Robert
The following changes since commit fa0b01082fb0596959841e95af8c516ae3f267a7:
admin: fix dependency display and search (2017-12-21 16:14:17 +1300)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib rbt/LI
http://git.pokylinux.org/cgit.cgi//log/?h=rbt/LI
Robert Yang (5):
utils.py: fix remove obsolete dependencies
update.py: make sure oe-core is fetched
update.py: fetch repos parallelly
update_layer.py: use it as a module
update_layer.py: only call init_parser when needed
layerindex/update.py | 176 +++++++++++++++++++++++----------------------
layerindex/update_layer.py | 146 +++++++++++--------------------------
layerindex/utils.py | 6 +-
settings.py | 2 +
4 files changed, 137 insertions(+), 193 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-03 5:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 5:42 Robert Yang [this message]
2018-01-16 1:52 ` [layerindex-web][PATCH 0/5] update.py: performance improve and 2 fixes Robert Yang
2018-02-01 4:59 ` Robert Yang
2018-02-04 23:33 ` Paul Eggleton
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=cover.1514957220.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=paul.eggleton@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.