All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Fixing ipkg-make-index slowness
Date: Fri, 05 Jan 2007 11:52:44 +0000	[thread overview]
Message-ID: <1167997964.5601.31.camel@localhost.localdomain> (raw)
In-Reply-To: <76520598.20070105093334@gmail.com>

Paul,

On Fri, 2007-01-05 at 09:33 +0200, Paul Sokolovsky wrote:
> 1. md5sum thrashing
> 
> In the summer, RP introduced patch for i-m-i ironically called
> index_speedup.patch:

There is nothing ironic about it, it does speed up the process ;-).
md5suming the files was faster than actually parsing them.

> Richard, what were the reasons for such conservative file matching?
> Filename matching should be just enough, as per OE convention, any
> package source changes leading to changes in the package metadata must
> lead to bumping of package recipe's PR, and that in turn updates package
> filename. Whoever don't follow PR update convention either call for
> trouble, and no checks could really help them, or know what they do
> (like bother to rebuild Packages from scratch). In this regard,
> checking ipk size is the great convenience for adventurous, because
> it's really high probability that update of any package metadata will
> lead to change of file size due to compression. In other words, I
> propose to remove md5sum check.

See Koen's reply.

The way forward is to store more information in the index, namely the
last modified timestamp for the file. If you add that and compare
timestamp+size, you can safely skip the md5sum check.

I can't remember why I didn't do that, it could have been a time thing.
It does mean adding a new field to the Packages file and that could also
have had implications elsewhere, I can't remember...

Richard




      parent reply	other threads:[~2007-01-05 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05  7:33 Fixing ipkg-make-index slowness Paul Sokolovsky
2007-01-05  9:21 ` Koen Kooi
2007-01-05  9:33   ` Paul Sokolovsky
2007-01-05  9:59     ` Koen Kooi
2007-01-05 11:52 ` Richard Purdie [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=1167997964.5601.31.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.