From: Ian Lance Taylor <iant@google.com>
To: overseers@gcc.gnu.org
Subject: [Michael Matz] Re: Don't let search bots look at buglist.cgi
Date: Tue, 17 May 2011 14:26:00 -0000 [thread overview]
Message-ID: <mcript9z9mu.fsf@coign.corp.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 41 bytes --]
fche: a comment about MnoGoSearch.
Ian
[-- Attachment #2: Type: message/rfc822, Size: 3077 bytes --]
From: Michael Matz <matz@suse.de>
To: Ian Lance Taylor <iant@google.com>
Cc: Richard Guenther <richard.guenther@gmail.com>, Andrew Haley <aph@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: Don't let search bots look at buglist.cgi
Date: Tue, 17 May 2011 13:12:23 +0200 (CEST)
Message-ID: <Pine.LNX.4.64.1105171307390.1989@wotan.suse.de>
Hi,
On Mon, 16 May 2011, Ian Lance Taylor wrote:
> >>> httpd being in the top-10 always, fiddling with bugzilla URLs?
> >>> (Note, I don't have access to gcc.gnu.org, I'm relaying info from
> >>> multiple instances of discussion on #gcc and richi poking on it;
> >>> that said, it still might not be web crawlers, that's right, but
> >>> I'll happily accept
> >>> _any_ load improvement on gcc.gnu.org, how unfounded they might seem)
>
> I think that simply blocking buglist.cgi has dropped bugzilla off the
> immediate radar. It also seems to have lowered the load, although I'm
> not sure if we are still keeping historical data.
Btw. FWIW, I had a quick look at one of the httpd log files, and in seven
hours on last Saturday (from 5:30 to 12:30), there were overall 435203 GET
requests, and 391319 of them came from our own MnoGoSearch engine, that's
90%. Granted many are then in fact 304 (not modified) responses, but
still, perhaps the eagerness of our own crawler can be turned down a bit.
Ciao,
Michael.
next reply other threads:[~2011-05-17 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 14:26 Ian Lance Taylor [this message]
2011-05-17 16:42 ` Christopher Faylor
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=mcript9z9mu.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=overseers@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).