[llvm-dev] GitHub Hooks
Renato Golin via llvm-dev
llvm-dev at lists.llvm.org
Tue Jul 19 15:32:57 PDT 2016
On 19 July 2016 at 23:16, Mehdi Amini <mehdi.amini at apple.com> wrote:
>> In the past, we were hit by web spiders that ignored completely the
>> robots.txt file. Anton has made that better, but it can escalate if
>> the spider realise we blocked them. There are ways to work around, but
>> not without accidentally blocking innocent people (mostly in China).
> That’s not relevant: this is about the WWW server, it does not have to be related to the hosting the repos.
No, this is about hosting the SVN server. The SVN view was disabled
for months this year before we could really see what was going on.
> Moving the SVN repo does not solve hosting videos, Debian packages, etc.
> I suspect most of the bandwidth does not come from `svn up` or `git pull`.
They share the same bandwidth, and sometimes the same server. It is relevant.
One thing making SVN slow was the amount of Debian packages being
downloaded form the same place.
> Like… proper hooks?
If we can work around it, and it seems we can, this is not such a big issue.
> You’re again conflating svn/git and hosting “binaries and videos”. I don’t think we ever planned to host these on github?
No, but they all share bandwidth. We moved videos to Youtube to
offload the bandwidth, and moving the code to GitHub shares the same
> Possibly, I don’t know, but that’s exactly why I asked for first hand data on the subject (i.e. Anton and/or Tanya) about hosting the git/SVN repos themselves, instead of hand-wavy “I believe” discussions.
Bear in mind that I gave you facts (bandwidth problems, turned off SVN
services, constant breakdowns, expertise in handling traffic, backup
I also made you aware that the human cost is not *just* Tanya and
Anton, but also me and everyone else that maintains buildbots,
external mirrors, etc. and it *is* larger than the hardware costs. You
just don't see it because we're all volunteers.
Branding them as "hand-wavy I believe" is *not* appropriate.
More information about the llvm-dev