From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3611 invoked by alias); 5 Apr 2004 19:36:45 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 3584 invoked from network); 5 Apr 2004 19:36:38 -0000 Received: from unknown (HELO dair.pair.com) (209.68.1.49) by sources.redhat.com with SMTP; 5 Apr 2004 19:36:38 -0000 Received: (qmail 92501 invoked by uid 20157); 5 Apr 2004 19:36:34 -0000 Date: Mon, 05 Apr 2004 19:36:00 -0000 From: Hans-Peter Nilsson X-X-Sender: hp@dair.pair.com To: David Edelsohn cc: overseers@sources.redhat.com Subject: Re: htdig and sources.redhat.com loadavg In-Reply-To: <200404051849.i35InoT27980@makai.watson.ibm.com> Message-ID: References: <200404051849.i35InoT27980@makai.watson.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2004-q2/txt/msg00029.txt.bz2 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: > > 15:56:05 up 45 days, 17:01, 1 user, load average: 23.58, 23.54, 25.16 > 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