All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <yocto@yoctoproject.org>, <paul.eggleton@linux.intel.com>
Subject: [PATCH 0/4][layerindex-web] bug fix and performance improve
Date: Wed, 18 Apr 2018 19:04:29 +0800	[thread overview]
Message-ID: <cover.1524049072.git.liezhi.yang@windriver.com> (raw)

Hi Paul,

The patch 4 can improve a lot on update.py (up to 98%), here is the testing
data, please feel free to give your comments.

$ time update.py -b master --nofetch [--fullreload]

                   Before    Now       Reduced
No update:         276s      3.6s      98%
Partial update:    312s      87s       72%
Full repload:      1016s     980s      3%

Note:
* All of the testing are based on --nofetch

* "No update" means all layers on the branch is up-to-date, for
  example, when we run it twice, there is no update in the second run, so we
  only need about 3s now, which is the most common case when we use cron to run
  it per half an hour.

* "Partly update" means part of the layers have been updated.

* "Fullreload" means all of the layers have been updated.

// Robert

The following changes since commit 611c96883c35240d3c291951146154d828745774:

  requirements.txt: use the most recent Django 1.8 version (2018-03-26 08:29:27 +1300)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib rbt/layerindex
  http://git.pokylinux.org/cgit.cgi//log/?h=rbt/layerindex

Robert Yang (4):
  fixup! update: don't stop on unsatisfied layer dependencies
  update.py: add an option --timeout for lockfile
  update.py: print failed layers summary in the end
  update_layer.py: move layer validation to update.py (Performance
    improve)

 layerindex/update.py       | 97 ++++++++++++++++++++++++++++++++++++++++++++--
 layerindex/update_layer.py | 39 ++-----------------
 layerindex/utils.py        | 14 +++++--
 3 files changed, 108 insertions(+), 42 deletions(-)

-- 
2.7.4



             reply	other threads:[~2018-04-18 10:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-18 11:04 Robert Yang [this message]
2018-04-18 11:04 ` [PATCH 1/4] fixup! update: don't stop on unsatisfied layer dependencies Robert Yang
2018-04-18 11:04 ` [PATCH 2/4] update.py: add an option --timeout for lockfile Robert Yang
2018-04-18 11:04 ` [PATCH 3/4] update.py: print failed layers summary in the end Robert Yang
2018-04-18 11:04 ` [PATCH 4/4] update_layer.py: move layer validation to update.py (Performance improve) Robert Yang
2018-04-18 20:55   ` Paul Eggleton
2018-04-19  6:45     ` Robert Yang
2018-04-20  2:57       ` Paul Eggleton
2018-04-23  1:55   ` Paul Eggleton
2018-04-23  3:06     ` Robert Yang
2018-04-23  3:35       ` Paul Eggleton
2018-04-23  4:23         ` Robert Yang
2018-04-18 11:12 ` [PATCH 0/4][layerindex-web] bug fix and performance improve Burton, Ross
2018-04-19  6:49   ` Robert Yang

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.1524049072.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.