From: Michael Matz <matz@suse.de>
To: Andrew Haley <aph@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Don't let search bots look at buglist.cgi
Date: Mon, 16 May 2011 13:45:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1105161527360.1989@wotan.suse.de> (raw)
In-Reply-To: <4DD125C8.8090105@redhat.com>
Hi,
On Mon, 16 May 2011, Andrew Haley wrote:
> > It routinely is. bugzilla performance is terrible most of the time
> > for me (up to the point of five timeouts in sequence), svn speed is
> > mediocre at best, and people with access to gcc.gnu.org often observe
> > loads > 25, mostly due to I/O .
>
> And how have you concluded that is due to web crawlers?
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)
Ciao,
Michael.
next prev parent reply other threads:[~2011-05-16 13:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 19:19 Ian Lance Taylor
2011-05-16 12:59 ` Richard Guenther
2011-05-16 13:17 ` Andrew Haley
2011-05-16 13:18 ` Michael Matz
2011-05-16 13:28 ` Andrew Haley
2011-05-16 13:32 ` Andreas Schwab
2011-05-16 13:34 ` Richard Guenther
2011-05-16 13:39 ` Andrew Haley
2011-05-16 13:42 ` Michael Matz
2011-05-16 13:42 ` Andrew Haley
2011-05-16 13:45 ` Michael Matz [this message]
2011-05-16 14:18 ` Andrew Haley
2011-05-16 14:37 ` Richard Guenther
2011-05-16 15:28 ` Andrew Haley
2011-05-17 7:17 ` Ian Lance Taylor
2011-05-17 11:12 ` Axel Freyn
2011-05-17 13:39 ` Michael Matz
2011-05-16 23:13 ` Ian Lance Taylor
2011-05-17 2:53 ` Joseph S. Myers
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=Pine.LNX.4.64.1105161527360.1989@wotan.suse.de \
--to=matz@suse.de \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).