Re: gitweb testing and benchmarking (was: [PATCH 0/4] gitweb: Some improvements)

From: Jakub Narebski <jnareb@gmail.com>
Date: Sep 5, 2006, 08:59 UTC
Message-ID: <edje8a$sdo$1@sea.gmane.org>
In-Reply-To: <ediea9$d3d$2@sea.gmane.org>

Jakub Narebski wrote:

Show 16 quoted lines

> Junio C Hamano wrote:
>
>> It is a while since I tried gitweb on my machine the last time
>> but was it always this slow I wonder...  We probably would need
>> a good benchmark and automated test before going too much
>> further.
> 
> The problem is that before commit 5d043a3d856bd40d8b34b8836a561e438d23573b
>   gitweb: fill in gitweb configuration by Makefile
> by Martin Waitz one had to modify gitweb script to change
> the configuration from default.
> 
> But benchmarking is good. Simple time to run script from command line,
> with environment variables GATEWAY_INTERFACE="CGI/1.1", HTTP_ACCEPT="*/*",
> REQUEST_METHOD="GET" and of course QUERY_STRING set, and perhaps using
> ApacheBench.

I think that for testing gitweb we will be better with creating some twisted test repository (c.f. t/t4114-apply-typechange.sh), but for benchmarking it would be better to use some larger repository, for example git repository cut-off from above at some version (including tags!). Is there a way to do that?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git