Mailing-List: contact infrastructure-dev-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: infrastructure-dev@apache.org
Received-SPF: pass (nike.apache.org: domain of justin.erenkrantz@gmail.com
 designates 72.14.220.159 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=OWqSgxg9+ScktloG93dhgkvxp3goXcb9rs0Zuwhh5SHzf53kY88OLv2J5d8PPATTeIizBtYtbHBTc9XcOoQ4rF41RSgOvOjWUaSvnQ+H9IzA22i/YGtUkgXaw7WRX9SjsInMlQFYe/7Jwd2jfmV3ZJdqhhyRNJkHZlMMWOdeCG4=
Message-ID: <5c902b9e0805021150t7967f271r3cbc24d004bf2a62@mail.gmail.com>
Date: Fri, 2 May 2008 11:50:55 -0700
From: "Justin Erenkrantz" <justin@erenkrantz.com>
Sender: justin.erenkrantz@gmail.com
To: infrastructure-dev@apache.org
Subject: Re: Best Practices so far?
In-Reply-To: <481B55B6.20904@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <481ACF4C.9040509@gmail.com>
	 <510143ac0805020143y47fb22f9m6da17a123be7e130@mail.gmail.com>
	 <510143ac0805020507m302bcbfcje3d77bf9e6437722@mail.gmail.com>
	 <510143ac0805020739s1f0bc6e4t1fd45e3f563c633@mail.gmail.com>
	 <481B3378.30709@apache.org>
	 <fbdc6a970805020849p523b895dh7dec36211e6d5349@mail.gmail.com>
	 <5c902b9e0805020930l1bace3b3vbe2eaaa55ee4a08e@mail.gmail.com>
	 <481B55B6.20904@apache.org>

On Fri, May 2, 2008 at 10:56 AM, Grzegorz Kossakowski
<gkossakowski@apache.org> wrote:
>  Justin, pardon my ignorance, but do you know any tool that imports whole
> repository history without making many requests to our svn servers? You
> already support fisheye, ohloh and similar services. Aren't they putting
> lots of load at *initial* stage?

The Fisheye guys know to contact us before importing history as they
know that they have routinely brought the machine down.  AFAICT, Ohloh
hasn't worked off SVN but rather off releases - and, to the best of my
knowledge, they haven't tripped any of our DoS measures...yet.

>  Personally, I don't understand what's exactly your problem with me using
> git-svn.

I only care as much as you don't place an unreasonable drain on our
public services.  If it takes 100x more compute and network power to
service git-svn than a normal svn client, then our capacity is blown
out of the water.

I have to provision the resources as best as I can given the ASF's
constraints.  We don't have an endless amount of CPU or network cycles
to spend on users using tools that are inefficient and deny service to
others.  If you'd like to donate either your time or money to seeing
we have the service you desire, it's appreciated.  Until then, I have
to make the decision that serves the most people.  -- justin