From: "Shawn O. Pearce" <spearce@spearce.org>
To: thisnukes4u@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Summer of Code - Cached Packs/Object Lists
Date: Sun, 22 Mar 2009 18:59:36 -0700 [thread overview]
Message-ID: <20090323015936.GM23521@spearce.org> (raw)
In-Reply-To: <fsmi80et2dp57f5bdxUYAxe124vaj_firegpg@mail.gmail.com>
Please line wrap your email at something useful to others when
quoting, like 70-72 characters per line.
thisnukes4u@gmail.com wrote:
> I am particularly interested in the packfile caching project
> mentioned on the wiki, but I have a couple of questions:
>
> 1. Would it be possible to implement both the packfile and
> object list caching mechanisms, or might would one interfere with
> the other in some way?
You could do both. But I think most people on the list will argue
that doing both is overkill and only one is necessary, and further,
that only the one that offers the "biggest bank for the buck"
should be implemented.
Whole pack file caching has been discussed on list a few times as a
nice feature to have, but it raises some issues of cache management,
not to mention the issue I posed about it being relatively useless
on frequently changing repositories.
> 2. With just a quick perusal of the daemon source, I noticed
> that it shells out to the upload-pack command. Where would it be
> appropriate to implement such a caching mechanism, in the daemon
> proper, the upload-pack code, or would both need to be updated?
The daemon doesn't get enough data from the client in order to
perform any sort of caching.
So the caching has to happen in upload-pack, and/or pack-objects.
(upload-pack forks out to pack-objects to create the pack file to
send to the client)
--
Shawn.
next prev parent reply other threads:[~2009-03-23 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 1:53 Summer of Code - Cached Packs/Object Lists thisnukes4u
2009-03-23 1:59 ` Shawn O. Pearce [this message]
2009-03-23 2:49 ` Thomas Coppi
2009-03-23 2:52 ` Shawn O. Pearce
2009-03-23 14:41 ` Nicolas Pitre
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=20090323015936.GM23521@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=thisnukes4u@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 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.