All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Duchier <duchier@ps.uni-sb.de>
To: Tomas Mraz <t8m@centrum.cz>
Cc: duchier@ps.uni-sb.de, gnu-arch-dev@lists.seyza.com,
	talli@museatech.net, git@vger.kernel.org, torvalds@osdi.org
Subject: Re: [Gnu-arch-users] Re: [GNU-arch-dev] [ANNOUNCEMENT] /Arch/ embraces `git'
Date: Thu, 21 Apr 2005 11:09:58 +0200	[thread overview]
Message-ID: <86d5soa42h.fsf@speedy.lifl.fr> (raw)
In-Reply-To: <1114036849.5880.61.camel@perun.redhat.usu> (Tomas Mraz's message of "Thu, 21 Apr 2005 00:40:48 +0200")

Tomas Mraz <t8m@centrum.cz> writes:

> If we suppose the maximum number of stored blobs in the order of milions
> probably the optimal indexing would be 1 level [0:2] indexing or 2
> levels [0:1] [2:3]. However it would be necessary to do some
> benchmarking first before setting this to stone.

As I have suggested in a previous message, it is trivial to implement adaptive
indexing: there is no need to hardwire a specific indexing scheme.  Furthermore,
I suspect that the optimal size of subkeys may well depend on the filesystem.
My experiments seem to indicate that subkeys of length 2 achieve an excellent
compromise between discriminatory power and disk footprint on ext2.

Btw, if, as you indicate above, you do believe that a 1 level indexing should
use [0:2], then it doesn't make much sense to me to also suggest that a 2 level
indexing should use [0:1] as primary subkey :-)

Cheers,

-- 
Dr. Denys Duchier - IRI & LIFL - CNRS, Lille, France
AIM: duchierdenys

  reply	other threads:[~2005-04-21  9:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 10:00 [ANNOUNCEMENT] /Arch/ embraces `git' Tom Lord
2005-04-20 10:19 ` Miles Bader
2005-04-20 17:15 ` duchier
2005-04-20 22:40   ` [Gnu-arch-users] Re: [GNU-arch-dev] " Tomas Mraz
2005-04-21  9:09     ` Denys Duchier [this message]
2005-04-21 10:21       ` Tomas Mraz
2005-04-21 11:46         ` [Gnu-arch-users] " duchier
2005-04-20 22:51   ` Tomas Mraz
2005-04-21 19:04     ` Tom Lord
2005-04-21 20:35     ` [Gnu-arch-users] Re: [GNU-arch-dev] " Tom Lord
2005-04-20 23:04   ` Tom Lord
2005-04-21  0:05     ` [Gnu-arch-users] Re: [GNU-arch-dev] " Denys Duchier
2005-04-21 20:39       ` [Gnu-arch-users] " Tom Lord
2005-04-21  7:49     ` Tomas Mraz
2005-04-21 21:51       ` [Gnu-arch-users] Re: [GNU-arch-dev] " Tom Lord
2005-04-21 21:52       ` Tom Lord
2005-04-22 16:13       ` Linus Torvalds
2005-04-22 17:39         ` Edésio Costa e Silva
2005-04-20 21:31 ` Petr Baudis
2005-04-20 21:55   ` C. Scott Ananian
2005-04-20 22:22     ` chunking (Re: [ANNOUNCEMENT] /Arch/ embraces `git') Linus Torvalds
2005-04-20 23:42       ` C. Scott Ananian
2005-04-22 21:02       ` blowing chunks (quick update) C. Scott Ananian

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=86d5soa42h.fsf@speedy.lifl.fr \
    --to=duchier@ps.uni-sb.de \
    --cc=git@vger.kernel.org \
    --cc=gnu-arch-dev@lists.seyza.com \
    --cc=t8m@centrum.cz \
    --cc=talli@museatech.net \
    --cc=torvalds@osdi.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.