From: Nicolas Pitre <nico@cam.org>
To: Martin Koegler <mkoegler@auto.tuwien.ac.at>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] basic threaded delta search
Date: Fri, 07 Sep 2007 12:19:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.9999.0709071211420.21186@xanadu.home> (raw)
In-Reply-To: <20070907061105.GA1379@auto.tuwien.ac.at>
On Fri, 7 Sep 2007, Martin Koegler wrote:
> On Thu, Sep 06, 2007 at 10:48:06AM -0400, Nicolas Pitre wrote:
> > On Thu, 6 Sep 2007, Junio C Hamano wrote:
> > > Also how would this interact with the LRU
> > > delta base window we discussed a week or two ago?
> >
> > This is completely orthogonal.
>
> Maybe we should adjust the split point of the the object list so, that
> objects with the same name hash are processed by one thread, as the LRU
> could provide the most benefit for these objects.
>
> I think of something like (totally untested):
> for (i = 0; i < NR_THREADS; i++) {
> unsigned sublist_size = list_size / (NR_THREADS - i);
> + while (sublist_size < list_size && list[0]->hash == list[1]->hash)
> + sublist_size++;
I guess you mean list[sublist_size-1]->hash == list[sublist_size]->hash.
But yeah that is a good idea.
Nicolas
prev parent reply other threads:[~2007-09-07 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 6:13 [PATCH] straighten the list of objects to deltify Nicolas Pitre
2007-09-06 6:13 ` [PATCH] localize window memory usage accounting Nicolas Pitre
2007-09-06 6:13 ` [PATCH] rearrange delta search progress reporting Nicolas Pitre
2007-09-06 6:13 ` [PATCH] basic threaded delta search Nicolas Pitre
2007-09-06 6:19 ` David Kastrup
2007-09-06 6:23 ` Nicolas Pitre
2007-09-06 7:01 ` Junio C Hamano
2007-09-06 14:48 ` Nicolas Pitre
2007-09-07 6:11 ` Martin Koegler
2007-09-07 16:19 ` Nicolas Pitre [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.0.9999.0709071211420.21186@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mkoegler@auto.tuwien.ac.at \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).