From: Richard Guenther <rguenther@suse.de>
To: overseers@gcc.gnu.org
Subject: bugzilla slowness
Date: Wed, 19 Sep 2012 13:50:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1209191544470.28649@zhemvz.fhfr.qr> (raw)
When you do a change to a bug that triggers e-mails to be sent
bugzilla is extremely slow (you can hit "stop" in your browser
after a few seconds and continue happily). I think it was tracked
down to synchronous e-mail sending and outgoing spam verification.
Time spent seems to scale with the number of people CCed in a bug.
Can we please white-list gcc.gnu.org accounts?
This really makes bugzilla triage as part of release-manager duties
extremely painful and time consuming.
Thanks,
Richard.
next reply other threads:[~2012-09-19 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 13:50 Richard Guenther [this message]
2012-09-19 14:07 ` Paolo Carlini
2012-09-19 15:53 ` Frank Ch. Eigler
2012-09-19 16:46 ` Andreas Schwab
2012-09-19 21:12 ` Frank Ch. Eigler
2012-09-20 14:55 ` Richard Guenther
2012-10-13 16:29 Markus Trippelsdorf
2012-10-13 17:02 ` Ian Lance Taylor
2012-10-13 17:40 ` Markus Trippelsdorf
2012-10-13 18:14 ` Markus Trippelsdorf
2012-10-13 19:36 ` Frank Ch. Eigler
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=alpine.LNX.2.00.1209191544470.28649@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--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).