From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Running gitweb under mod_perl
Date: Tue, 05 Sep 2006 22:32:21 +0200 [thread overview]
Message-ID: <edkms4$mr9$1@sea.gmane.org> (raw)
In-Reply-To: 20060824140525.G638085b@leonov.stosberg.net
Dennis Stosberg wrote:
> Jakub Narebski wrote:
>
>> What should I put in Apache configuration (Apache 2.0.54 if this
>> matters, mod_perl 2.0.1)
>
> From my configuration:
>
> <Directory /home/dennis/public_html/perl>
> Options -Indexes +ExecCGI
> AllowOverride None
> PerlSendHeader On
> SetHandler perl-script
> PerlHandler ModPerl::Registry
> </Directory>
I use mod_perl 2.0 version
Alias /perl /var/www/perl
<Directory /var/www/perl>
SetHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlOptions +ParseHeaders
Options +ExecCGI
</Directory>
What is strange that ApacheBench is showing that mod_perl is _slower_ than
CGI version: 3003.305 [ms] (mean) CGI vs 3500.589 [ms] (mean) mod_perl
for summary page for git.git repository (my copy that is).
I wonder if I misconfigured something...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-09-05 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 12:43 Running gitweb under mod_perl Jakub Narebski
2006-08-24 12:46 ` Johannes Schindelin
2006-08-24 14:05 ` Dennis Stosberg
2006-08-24 15:12 ` [PATCH] gitweb: Use --git-dir parameter instead of setting $ENV{'GIT_DIR'} Dennis Stosberg
2006-08-28 15:49 ` [PATCH (amend)] " Jakub Narebski
2006-08-29 7:18 ` Dennis Stosberg
2006-08-29 7:19 ` [PATCH] use do() instead of require() to include configuration Dennis Stosberg
2006-09-05 20:32 ` Jakub Narebski [this message]
2006-08-24 17:49 ` Running gitweb under mod_perl Jakub Narebski
2006-08-24 19:32 ` Dennis Stosberg
2006-08-24 20:59 ` Jakub Narebski
2006-08-25 1:13 ` Randal L. Schwartz
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='edkms4$mr9$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.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).