git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Yann Simon <yann.simon.fr@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [JGIT] Questions about binary right shifting
Date: Thu, 5 Feb 2009 21:32:01 +0100	[thread overview]
Message-ID: <200902052132.01797.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20090205152108.GE26880@spearce.org>

torsdag 05 februari 2009 16:21:08 skrev Shawn O. Pearce:
> Yann Simon <yann.simon.fr@gmail.com> wrote:
> > I can see in the code that the signed right shifting is used.
> > Could it be a problem? Or do we manipulate only positive numbers?
> 
> Heh.  We shouldn't ever be dealing with a case where there are more
> than 1 billion files in the index, and thus we should never see
> the expression "low + high" wrap negative, and then try to divide
> by 2 here.
> 
> Binary search on a 1 billion file index would hurt, badly.  I'm not
Roughly three times the search time in the linux kernel repo. Not
that bad.

> sure what project even has 1 billion source files to checkout
> on disk.  Isn't that easily a 4 TB filesystem just for the ext2
Not even KDE or Eclipse.
> inodes of the working tree files?  :-)

> Oh, and we can't even have an index with 1 billion entries in it
> anyway.  DirCache.readFrom allocates a byte[] of entryCnt * 62.
> So our largest number of files permitted is 34,636,833, due to
> the limit on byte[] maxing out at 2 GB.  Thus high below cannot
> ever be larger than 34 million, and we can't wrap.
Assuming the whole index is in memory. But I guess we can discard
it as most competing systems choke on a lot lot less and for very
large indexes we get other problems with size. Binary search isn't
one of them. Having i packed index is probably the biggest issue
since it has to be completely rewritten when we add or remove
files. But, OK, we won't solve this unless we have a case. I think
our current challenge is dealing with 100k files real smoothly.

Patching this to make findbugs shut up is ok with me.

-- robin

      reply	other threads:[~2009-02-05 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 14:37 [JGIT] Questions about binary right shifting Yann Simon
2009-02-05 15:21 ` Shawn O. Pearce
2009-02-05 20:32   ` Robin Rosenberg [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=200902052132.01797.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=yann.simon.fr@gmail.com \
    /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 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 NNTP newsgroup(s).