public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: overseers@sources.redhat.com
Subject: Re: htdig and sources.redhat.com loadavg
Date: Mon, 05 Apr 2004 19:36:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.58.0404051515280.67829@dair.pair.com> (raw)
In-Reply-To: <200404051849.i35InoT27980@makai.watson.ibm.com>

On Mon, 5 Apr 2004, David Edelsohn wrote:
> 	The load average on sources.redhat.com appears to be spiking very
> high on Monday, according to reports from people who can log in:
>
> <dnovillo>  15:56:05  up 45 days, 17:01,  1 user,  load average: 23.58, 23.54, 25.16
> <echristo>  18:31:24  up 45 days, 19:36,  2 users,  load average: 37.94, 37.67, 35.41
>
> htdig is a candidate for the root cause of the problem.  The heavy disk
> traffic and decrease in performance from htdig is generating a backlog of
> CVS operations -- 24 cvs processes in disk wait state, which further loads
> the system.
>
> 	An informal poll of the 30+ people on the #gcc IRC channel did not
> find anyone who felt htdig was useful relative to other search options.
> Four channel members suggested disabling htdig, so I would I like propose
> that to overseers.  The performance problem of sources.redhat.com on
> Monday is impacting development.

Please be informed that htdig is used on the gcc side and
sourceware side (all other projects) separately.  I don't think
what's said on #gcc shouldn't be final (or perhaps shouldn't
matter at all) for the sourceware side.

I have no problem shutting down htdig for gcc permanently.

Though it seems it wasn't considered that there could be an
error situation that led to the high load from htdig.  I just
looked and there was; a DB file is over the 2G limit once again,
and the last two updates (done every other day for gcc htdig)
have failed.  Since the updates have been from scratch and the
scripts retries once in case of failure, the load from htdig has
been much higher that what is normal.  I've shut off gcc htdig
until I get to investigate whether it's fixable (once again).

(Everyone ok with shutting off gcc htdig permanently?)

brgds, H-P

  reply	other threads:[~2004-04-05 19:36 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 18:50 David Edelsohn
2004-04-05 19:36 ` Hans-Peter Nilsson [this message]
2004-04-05 19:46   ` Phil Edwards
2004-04-05 19:56     ` Frank Ch. Eigler
2004-04-05 20:03       ` Phil Edwards
2004-04-05 20:36     ` Hans-Peter Nilsson
2004-04-05 21:15       ` Phil Edwards
2004-04-05 21:23         ` Hans-Peter Nilsson
2004-04-05 21:46           ` Phil Edwards
2004-04-05 22:11             ` Hans-Peter Nilsson
2004-04-05 22:26               ` Phil Edwards
2004-04-05 20:48     ` Benjamin Kosnik
2004-04-05 20:52       ` Ian Lance Taylor
2004-04-05 20:57         ` Zack Weinberg
2004-04-08 21:18         ` Gerald Pfeifer
2004-04-05 21:12   ` Hans-Peter Nilsson
2004-04-05 20:51 ` Christopher Faylor
2004-04-05 21:21   ` Matthew Galgoci
2004-04-05 23:36     ` Zack Weinberg
2004-04-06  0:06       ` Matthew Galgoci
2004-04-06  0:17         ` Matthew Galgoci
2004-04-06  0:29         ` Zack Weinberg
     [not found]   ` <cgf@alum.bu.edu>
2004-04-05 21:03     ` David Edelsohn
2004-04-05 21:08       ` Ian Lance Taylor
     [not found]         ` <ian@airs.com>
2004-04-05 21:14           ` David Edelsohn
2004-04-05 22:51             ` Jason Molenda
2004-04-05 23:39               ` GCC snapshot generation (was Re: htdig and sources.redhat.com loadavg) Zack Weinberg
2004-04-06 14:49     ` htdig and sources.redhat.com loadavg David Edelsohn
2004-04-06 16:18       ` Jonathan Larmour
2004-04-06 16:25         ` David Edelsohn
2004-04-06 16:34         ` Ian Lance Taylor
2004-04-06 16:39           ` Phil Edwards
2004-04-07  2:58           ` Christopher Faylor
2004-04-06 16:41         ` Ian Lance Taylor
2004-04-07  2:59           ` Christopher Faylor
2004-04-06 17:40     ` David Edelsohn
2004-04-06 18:00       ` Jonathan Larmour
2004-04-06 19:43         ` Hans-Peter Nilsson
2004-04-06 19:52           ` Frank Ch. Eigler
2004-04-06 23:24             ` Hans-Peter Nilsson
2004-04-06 19:52           ` Ian Lance Taylor
2004-04-08 14:48     ` gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 14:53       ` Frank Ch. Eigler
2004-04-08 15:18         ` Christopher Faylor
2004-05-02 11:32     ` sourceware load problem again? David Edelsohn
2004-04-08  4:04 gcc.gnu.org CVS meta-data corrupt? David Edelsohn
2004-04-08 13:20 ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler
2004-04-08 14:13   ` David Edelsohn
2004-04-08 14:21     ` Christopher Faylor
2004-04-08 13:42 ` Frank Ch. Eigler
2004-04-08 13:54   ` system rebooted (was Re: gcc.gnu.org CVS meta-data corrupt?) Christopher Faylor
2004-04-29 19:40 sourceware load problem again? David Edelsohn
2004-04-29 19:45 ` 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=Pine.BSF.4.58.0404051515280.67829@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=dje@watson.ibm.com \
    --cc=overseers@sources.redhat.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).