From: "J.H." <warthog19@eaglescrag.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Frank Lichtenheld <frank@lichtenheld.de>,
Petr Baudis <pasky@suse.cz>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Support caching projects list
Date: Sun, 16 Mar 2008 15:37:28 -0700 [thread overview]
Message-ID: <1205707048.2758.35.camel@localhost.localdomain> (raw)
In-Reply-To: <200803161937.07082.jnareb@gmail.com>
On Sun, 2008-03-16 at 19:37 +0100, Jakub Narebski wrote:
> On Sun, 16 Mar 2008, J.H. wrote:
> > On Sun, 2008-03-16 at 12:41 +0100, Frank Lichtenheld wrote:
> >> On Sat, Mar 15, 2008 at 02:44:42PM -0700, Jakub Narebski wrote:
> >>>
> >>> This could be much simplified with perl-cache (perl-Cache-Cache).
> >>> Unfortunately this is non-standard module, not distributed (yet?)
> >>> with Perl.
> >>
> >> I think somebody who actually needs this can be bothered to install a
> >> CPAN perl module. This should probably not enabled by default anyway.
> >
> > The people who need the caching are also likely those who are most
> > averse to using things that don't either come with their distribution or
> > aren't easily and readily available in something like an extras
> > repository or a very well trusted contrib repository. I can at least
> > vouch for one large site that needs this that doesn't install things via
> > cpan for a lot of different reasons.
>
> Actually Cache::FileCache, which is part of CacheCache distribution,
> should be available in contrib or even extras repository. I have
> installed it as perl-Cache-Cache RPM (1.05-1.fc4.rf) on my Aurox 11.1
> (which is old Fedora Core 4 based distribution), from Dries RPM
> repository (part of FreshRPM now, IIRC).
That would be fine, I don't think the larger sites would have issues
finding a copy than.
>
> The problem is that at least according to what documentation of other,
> never CPAN modules says Cache::FileCache is slow, as it always serialize
> using Storable (Storable should be part of perl distribution).
That makes it much less interesting unfortunately.
> We can always install local copy alongside gitweb...
>
>
> P.S. When searching CPAN for existing modules for caching and CGI
> caching I have found Cache::Adaptive::ByLoad which does what
> caching-gitweb does, and some solutions in newer caching interfaces,
> either CHI or Cache which try to avoid thundering horde problem.
Interesting - my have to take a look at that.
> P.P.S. Does kernel.org use memcached, or some kind of web cache
> (reverse proxy cache) like Varnish or Squid?
No - doesn't buy us anything really unfortunately. And since I'm doing
caching inside of gitweb itself having multiple layers of caching just
makes things more complicated, adds unnecessary latency to updates, etc.
- John
next prev parent reply other threads:[~2008-03-16 22:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 23:14 [PATCH] gitweb: Support caching projects list Petr Baudis
2008-03-14 0:07 ` Jay Soffian
2008-03-14 0:22 ` Petr Baudis
2008-03-14 0:27 ` Jay Soffian
2008-03-14 0:30 ` J.H.
2008-03-14 12:17 ` Jakub Narebski
2008-03-14 0:36 ` J.H.
2008-03-17 17:49 ` repo.or.cz renovation Petr Baudis
2008-03-17 18:11 ` Petr Baudis
2008-03-17 18:44 ` J.H.
2008-03-17 20:41 ` Jakub Narebski
2008-03-17 21:09 ` Jakub Narebski
2008-03-14 15:29 ` [PATCH] gitweb: Support caching projects list Jakub Narebski
2008-03-14 21:11 ` Jay Soffian
2008-03-14 0:19 ` Junio C Hamano
2008-03-14 8:35 ` Frank Lichtenheld
2008-03-14 12:14 ` Jakub Narebski
2008-03-17 17:40 ` Petr Baudis
2008-03-15 21:44 ` Jakub Narebski
2008-03-16 0:56 ` Miklos Vajna
2008-03-16 11:41 ` Frank Lichtenheld
2008-03-16 16:52 ` J.H.
2008-03-16 18:37 ` Jakub Narebski
2008-03-16 22:37 ` J.H. [this message]
2008-03-16 23:39 ` Jakub Narebski
2008-03-17 18:10 ` repo.or.cz renovated Petr Baudis
2008-03-17 19:09 ` Junio C Hamano
2008-03-17 19:25 ` Petr Baudis
2008-03-17 19:34 ` Theodore Tso
2008-03-17 19:54 ` Petr Baudis
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=1205707048.2758.35.camel@localhost.localdomain \
--to=warthog19@eaglescrag.net \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).