From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Nix <nix@esperi.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Handling very large numbers of symbolic references?
Date: Tue, 25 Jul 2006 23:29:54 +0200 [thread overview]
Message-ID: <44C68D52.6030107@lsrfire.ath.cx> (raw)
In-Reply-To: <87psfteb4l.fsf@hades.wkstn.nix>
Nix schrieb:
> However, this causes a potential problem. There are tens of thousands of
> these bugs, and the .git/refs/heads directory gets *enormous* and thus
> the system gets terribly terribly slow (crappy old Solaris filesystem
> syndrome).
>
> It seems to me there are two ways to fix this:
>
> - restructure .git/refs/* in a similar way to .git/objects, i.e. as a
> one- or two-level tree.
Branch names are allowed to contain slashes, thus your porcelain is free
to implement such a tree. Add a slash after every two bug ID digits and
your directories will never contain more than 100 objects.
René
next prev parent reply other threads:[~2006-07-25 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 19:29 Handling very large numbers of symbolic references? Nix
2006-07-25 21:29 ` Rene Scharfe [this message]
2006-07-25 21:52 ` Nix
2006-07-25 22:23 ` Linus Torvalds
2006-07-25 23:08 ` Nix
2006-07-25 23:20 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 18:38 linux
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=44C68D52.6030107@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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).