unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Meyering <jim@meyering.net>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Savannah-hackers-public@gnu.org, emacs-devel@gnu.org,
	eggert@cs.ucla.edu
Subject: Re: [Savannah-hackers-public] Re: bzr + savannah.gnu.org slow again
Date: Mon, 28 Feb 2011 14:02:19 +0100	[thread overview]
Message-ID: <87d3mcpb1g.fsf@rho.meyering.net> (raw)
In-Reply-To: <1s62s437sp.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 28 Feb 2011 03:03:18 -0500")

Glenn Morris wrote:
> At 23.30 PST on Sunday 27 Feb, it is very slow again. ~ 35 mins for a ~ 5
> line commit. It was alright mid-afternoon PST.
>
> Can you not just disable the cgit service (it seems to still be
> available) until there is a solution for this problem? Being able to
> commit is more important.

Hi Glenn,

I've diagnosed and fixed the problem.  git.sv is now running a new binary.
The trigger was a buggy spider that was provoking an infloop in cgit.
Once there were 15-20 cgit.cgi process stuck in this infloop, the
system would become essentially unusable.

I've just fixed the cgit bug and reported it privately to upstream
and as http://bugzilla.redhat.com/680905 (private, for now).



  reply	other threads:[~2011-02-28 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26  6:21 bzr + savannah.gnu.org slow again Paul Eggert
2011-02-26  6:50 ` Paul Eggert
2011-02-26  7:54   ` Eli Zaretskii
2011-02-26  8:13     ` [Savannah-hackers-public] " Jim Meyering
2011-02-26  8:49       ` Eli Zaretskii
2011-02-26  9:06         ` Eli Zaretskii
2011-02-28  8:03           ` Glenn Morris
2011-02-28 13:02             ` Jim Meyering [this message]
2011-02-28 17:54               ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d3mcpb1g.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=Savannah-hackers-public@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).