public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: overseers@sources.redhat.com
Subject: Re: htdig and sources.redhat.com loadavg
Date: Tue, 06 Apr 2004 18:00:00 -0000	[thread overview]
Message-ID: <4072F04E.2050801@eCosCentric.com> (raw)
In-Reply-To: <200404061740.i36HeoT28142@makai.watson.ibm.com>

David Edelsohn wrote:
>  2949 anoncvs   15   0  3868 1528    76 S    45.3  0.0   2:44   1 cvs
> 24943 htdigid   15   0  379M  79M   408 D     1.7  3.9  36:42   1 htdig
> 
> Is 379M/79M for htdig really a good use of sourceware resources relative
> to buffer caches?

vmstat says:
>    procs                      memory      swap          io     system      cpu
>  r  b  w   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy id
>  0 29  0 645584  40872  24568 751668   11    0  3544   305 1043  1898 16 10 75


750+24Mb cache out of 2Gb total seems alright (obviously some of the page 
cache is exes, but most of those will be shared between identical 
processes), and the swapping figures are low so clearly its the 79Mb figure 
that's relevant which is nothing in comparison. sourceware is I/O bound in 
ways that buffers/page cache is unlikely to help. Unsurprisingly cvs 
checkouts in particular are likely to chew a lot of cache.

Remember that the htdig problems of yesterday were to do with the gcc side 
of the server. The htdig you are looking at is the sourceware side which 
should have no real problem (other than the load due to other processes on 
the server). The problems of today seem more likely to me to be people 
updating the cvs checkouts they didn't get yesterday. I certainly don't 
want htdig disabled with no replacement for eCos, but perhaps someone could 
consider doing:

kill -STOP 24943 ; sleep 3600; kill -CONT 24943

to give the rest of the system an opportunity to catch up.

It may be interesting to see what projects the anon cvs checkouts are for, 
as for example if they are gcc, then it may help for more to move to 
savannah's anon cvs server.

Jifl
-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
 >>>>> Visit us in booth 2527 at the Embedded Systems Conference 2004 <<<<<
March 30 - April 1, San Francisco http://www.esconline.com/electronicaUSA/
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  reply	other threads:[~2004-04-06 18:00 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
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 [this message]
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=4072F04E.2050801@eCosCentric.com \
    --to=jifl@ecoscentric.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).