public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor•com>
To: Christopher Li <git@chrisli•org>
Cc: git@vger•kernel.org
Subject: Re: Yet another base64 patch
Date: Wed, 13 Apr 2005 23:27:46 -0700	[thread overview]
Message-ID: <425E0D62.9000401@zytor.com> (raw)
In-Reply-To: <20050414024228.GC18655@64m.dyndns.org>

Christopher Li wrote:
> 
> But if you write a large number of random files, when htree has three
> levels index. htree will suffer on the effect that it dirty random block
> very quickly, most block get dirty only contain one or two new entries.
> Ext3 will choke on it due to the limited journal size.
> 
> While non-index directory, new entry are very compact on the blocks.
> So it end up dirty a lot less blocks, of course, lookup will suffer.
> 
> Depend on you want check out fast or write a big tree fast, you can't
> win it all.
> 

Actually, the subdirectory hack has the same effect, so you lose 
regardless.  Doesn't mean that you can't construct cases where the 
subdirectory hack doesn't win, but I maintain that those are likely to 
be artificial.

It's probably worth noting that you have to assume htree is on, since 
that's the typical default for a Linux installation, even if you use the 
subdirectory hack.

	-hpa

  reply	other threads:[~2005-04-14  6:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  4:19 Yet another base64 patch H. Peter Anvin
2005-04-14  2:24 ` Christopher Li
2005-04-14  5:36   ` H. Peter Anvin
2005-04-14  2:42     ` Christopher Li
2005-04-14  6:27       ` H. Peter Anvin [this message]
2005-04-14  6:35         ` H. Peter Anvin
2005-04-14  7:40         ` Linus Torvalds
2005-04-14 16:58           ` H. Peter Anvin
2005-04-14 17:42             ` Linus Torvalds
2005-04-14 19:11               ` bert hubert
2005-04-14 19:25                 ` H. Peter Anvin
2005-04-14 21:47                   ` bert hubert
2005-04-15  0:44                     ` Linus Torvalds
2005-04-15  1:06                       ` H. Peter Anvin
2005-04-17  4:10                         ` David Lang
2005-04-18  6:23                           ` H. Peter Anvin
2005-04-15  1:07                       ` H. Peter Anvin
2005-04-15  3:58                         ` Paul Jackson
2005-04-17  3:53                           ` David A. Wheeler
2005-04-17  4:05                             ` Paul Jackson
2005-04-17  6:38                               ` David A. Wheeler
2005-04-17  8:16                                 ` Paul Jackson
2005-04-17 17:51                                   ` David A. Wheeler
2005-04-17 18:19                                 ` Petr Baudis
2005-04-18  5:13                                   ` David A. Wheeler
2005-04-18 12:59                                     ` Kevin Smith
2005-04-18 16:42                                       ` David A. Wheeler
2005-04-17 14:30                               ` Daniel Barkalow
2005-04-17 16:29                                 ` David A. Wheeler
2005-04-14  4:25 ` H. Peter Anvin
2005-04-14  8:17 ` Linus Torvalds
2005-04-14 17:02   ` H. Peter Anvin
2005-04-15 23:55 ` Paul Dickson
2005-04-18  6:28   ` H. Peter Anvin

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=425E0D62.9000401@zytor.com \
    --to=hpa@zytor$(echo .)com \
    --cc=git@chrisli$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox