From: Michael Haggerty <mhagger@alum.mit.edu>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Gerd Knops <gerti@bitart.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Possible bug with branch names and case sensitivity
Date: Wed, 23 Nov 2011 09:54:45 +0100 [thread overview]
Message-ID: <4ECCB4D5.3090200@alum.mit.edu> (raw)
In-Reply-To: <CAG+J_DxREbykWggrD49L7qvR9M36wKL7+_kOYbvcWmLBCF2Gog@mail.gmail.com>
On 11/22/2011 06:31 PM, Jay Soffian wrote:
> I wonder what the downside would be of always using packed refs on
> case-insenstive file systems. This would seem analogous to how git no
> longer uses symlinks.
The theoretical downside is that when the total number of packed refs is
very large, it is more expensive to access or change a single ref if it
is packed than if it is loose (because the whole packed refs file has to
be read, parsed, then rewritten, and thus scales like O(N)). OTOH the
number of references must be quite large before loose references win,
because the constant factor for loose references is much larger than
that for packed references. I also believe that there is still scope
for optimizing the handling of packed references to make them yet faster
and perhaps even improve their scaling.
But I think that a lot of code would have to change to make this happen.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2011-11-23 8:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:08 Possible bug with branch names and case sensitivity Gerd Knops
2011-11-21 19:18 ` Jay Soffian
2011-11-22 5:21 ` Michael Haggerty
2011-11-22 17:31 ` Jay Soffian
2011-11-23 8:54 ` Michael Haggerty [this message]
2011-11-23 20:50 ` Ævar Arnfjörð Bjarmason
2011-11-23 22:08 ` Joshua Jensen
2011-11-22 17:49 ` Junio C Hamano
2011-11-23 9:22 ` Michael Haggerty
2011-11-23 18:59 ` Junio C Hamano
2011-11-22 18:01 ` Junio C Hamano
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=4ECCB4D5.3090200@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=gerti@bitart.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@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).