From: Petr Baudis <pasky@suse.cz>
To: Lea Wiemann <lewiemann@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org, John Hawley <warthog19@eaglescrag.net>,
Junio C Hamano <gitster@pobox.com>,
Lars Hjemli <hjemli@gmail.com>
Subject: Re: Gitweb caching: Google Summer of Code project
Date: Fri, 30 May 2008 17:07:13 +0200 [thread overview]
Message-ID: <20080530150713.GG593@machine.or.cz> (raw)
In-Reply-To: <4840166C.3030903@gmail.com>
On Fri, May 30, 2008 at 04:59:56PM +0200, Lea Wiemann wrote:
> Jakub Narebski wrote:
>> IIRC the policy usually is that one can install packages
>> from main (base) repository for Linux distribution used on server,
>
> libcache-memcached-perl is in Debian stable; that's fair enough I think.
> Cache::Memcached::Fast doesn't seem to be in Debian as of now, but I
> wouldn't worry about performance unless it comes up.
Still, please make this optional. It is fine for gitweb not to do any
caching in the bare setup, but you should be able to get the simple
version running without any external dependencies.
>>>> By the way what do you think about adding (as an option) information
>>>> about gitweb performance to the [HTML] output,
>> I'd try to add it when I'd have a bot more of free time
>
> I'd probably wait with this until I've written the Perl Git API.
Hmm, it shouldn't depend on that in any way, should it?
use Time::HiRes qw(gettimeofday tv_interval);
my $t0 = [gettimeofday];
...
print "<p>This page took ".tv_interval($t0, [gettimeofday])."s to generate.</p>";
I wonder what oldest Perl versions do we aim to support? If <5.8, we
need to be more careful about Time::HiRes. It would be useful to
document this with a use perl statement at the top of the script.
--
Petr "Pasky" Baudis
Whatever you can do, or dream you can, begin it.
Boldness has genius, power, and magic in it. -- J. W. von Goethe
next prev parent reply other threads:[~2008-05-30 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 18:03 Gitweb caching: Google Summer of Code project Lea Wiemann
2008-05-27 21:53 ` Jakub Narebski
2008-05-27 22:54 ` Lea Wiemann
2008-05-28 12:14 ` Jakub Narebski
2008-05-28 18:33 ` Lea Wiemann
2008-05-29 23:27 ` Jakub Narebski
2008-05-30 7:24 ` Lea Wiemann
2008-05-30 10:02 ` Jakub Narebski
2008-05-30 14:59 ` Lea Wiemann
2008-05-30 15:07 ` Petr Baudis [this message]
2008-05-30 15:27 ` Lea Wiemann
2008-05-30 15:38 ` Petr Baudis
2008-05-30 16:04 ` Rafael Garcia-Suarez
2008-05-30 18:56 ` J.H.
2008-05-30 20:28 ` Junio C Hamano
2008-05-30 21:32 ` Lea Wiemann
2008-05-30 18:47 ` Lea Wiemann
2008-05-31 10:15 ` 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=20080530150713.GG593@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hjemli@gmail.com \
--cc=jnareb@gmail.com \
--cc=lewiemann@gmail.com \
--cc=warthog19@eaglescrag.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 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).