From: linux@horizon.com
To: git@vger.kernel.org, junkio@cox.net
Cc: linux@horizon.com
Subject: Re: Cygwin can't handle huge packfiles?
Date: 6 Apr 2006 16:57:24 -0400 [thread overview]
Message-ID: <20060406205724.12216.qmail@science.horizon.com> (raw)
> Right now we LRU the pack files and evict older ones when we
> mmap too many, but the unit of eviction is the whole file, so it
> would not help the case like yours at all. It might be possible
> to mmap only part of a packfile, but it would involve fairly
> major surgery to sha1_file.c.
The simplest solution seems to be to limit pack file size to a reasonable
fraction of a 32-bit address space. Say, 0.5 G.
That should be a fairly straightforward hack to git-pack-objects.
It already emits two files; just make it emit more.
You can tweak the heurisitics to try to find a good break point: start
thinking about splitting the pack when you get to one size, but don't
force a break until you hit a harder limit as long as the deltas are
working well.
This can all be adjustable with a command line and/or config file option
to allow for the eventual demise of 32-bit systems.
next reply other threads:[~2006-04-06 20:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 20:57 linux [this message]
2006-04-06 23:53 ` Cygwin can't handle huge packfiles? Junio C Hamano
2006-04-07 3:05 ` linux
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 9:46 Kees-Jan Dijkzeul
2006-04-03 13:23 ` Johannes Schindelin
2006-04-03 14:26 ` Morten Welinder
2006-04-03 14:33 ` Linus Torvalds
2006-04-03 14:36 ` Linus Torvalds
2006-04-05 13:24 ` Kees-Jan Dijkzeul
2006-04-05 14:14 ` Johannes Schindelin
2006-04-05 21:08 ` Christopher Faylor
2006-04-05 23:27 ` Rutger Nijlunsing
2006-04-06 0:34 ` Christopher Faylor
2006-04-06 4:13 ` Junio C Hamano
2006-04-07 8:15 ` Junio C Hamano
2006-04-07 8:27 ` Jakub Narebski
2006-04-07 14:11 ` Nicolas Pitre
2006-04-07 18:31 ` Junio C Hamano
2006-04-07 18:46 ` Nicolas Pitre
2006-04-03 15:12 ` Johannes Schindelin
2006-04-03 14:38 ` Alex Riesen
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=20060406205724.12216.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.