From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, "J.H." <warthog9@eaglescrag.net>,
John 'Warthog9' Hawley <warthog9@kernel.org>
Subject: Re: [RFD] My thoughts about implementing gitweb output caching
Date: Sat, 8 Jan 2011 12:15:39 +0100 [thread overview]
Message-ID: <201101081215.42188.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1101072142550.22191@xanadu.home>
Nicolas Pitre wrote:
> On Fri, 7 Jan 2011, Jonathan Nieder wrote:
> > Jakub Narebski wrote:
> > > With output caching gitweb can also support 'Range' requests, which
> > > means that it would support resumable download. This would mean hat we
> > > would be able to resume downloading of snapshot (or in the future
> > > bundle)... if we cannot do this now. This would require some more code
> > > to be added.
> >
> > Exciting stuff.
> >
> > Teaching gitweb to generate bundles sounds like a recipe for high server
> > loads, though. I suspect manual (or by cronjob) generation would work
> > better, with a possible exception of very frequently cloned and
> > infrequently pushed-to repos like linus's linux-2.6.
>
> Even for Linus' linux repo, it is not a good idea to auto create bundle,
> except maybe once every major release which is every 3 months or so. I
> really don't think this is a good idea to put this in the realm of
> gitweb caching.
You are right, making gitweb aware of bundles (if they are put in some
specified place, e.g. .git/objects/pack or .git/objects/bundle) is I guess
a better idea than allowing for gitweb to generate bundles, perhaps
only if caching is enabled, and perhaps with very long expiration time.
Of course the standard way should be also the standard place for git
clients to find bundles in proposed extension to git-clone.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2011-01-08 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 23:42 [RFD] My thoughts about implementing gitweb output caching Jakub Narebski
2011-01-08 0:26 ` Jonathan Nieder
2011-01-08 2:46 ` Nicolas Pitre
2011-01-08 11:15 ` Jakub Narebski [this message]
2011-01-08 11:44 ` Jakub Narebski
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=201101081215.42188.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=nico@fluxnic.net \
--cc=warthog9@eaglescrag.net \
--cc=warthog9@kernel.org \
/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).