public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: overseers@sourceware.org
Subject: Re: Mercurial repository
Date: Wed, 30 May 2007 09:34:00 -0000	[thread overview]
Message-ID: <465D4504.30505@jifvik.org> (raw)
In-Reply-To: <4aca3dc20705291513l2ea0e41ds4f2063e448238c12@mail.gmail.com>

Daniel Berlin wrote:
> 
> I have thus installed mercurial, and it's web component (which is a
> simple python script) on sourceware.
> 
> The mirror is publicly available, and I am watching our logs and load
> from it to make sure it's not taking up a lot of cpu (so far, it is
> taking up roughly nothing).

It was observed before the recent reboot that sourceware was exhibiting a 
high level of disk activity, contributing to a high overall load, resulting 
in things like dropped anonsvn/cvs connections etc.  The nature of disk 
activity is that it's difficult to point the finger at the precise cause, 
but the mercurial script that pulls from svn seemed to be cropping up a lot.

So if you're going to be monitoring mercurial, please also consider its 
effect on disk, not just CPU. This won't show up in 'top' etc.

For now though, the load seems lower, and I couldn't say for definite what 
the difference is, but I do note the mercurial scripts no longer seem to be 
running (since the reboot).

Have a look at http://sourceware.org/mrtg/summary.html and in particular 
note http://sourceware.org/mrtg/pageio.html and how it changes at start of 
week 20. I don't know whether, if or how that corresponds to when mercurial 
(or the mercurial pull from svn script) started operation.

Jifl
-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  reply	other threads:[~2007-05-30  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 22:13 Daniel Berlin
2007-05-30  9:34 ` Jonathan Larmour [this message]
2007-05-30 16:54   ` Daniel Berlin

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=465D4504.30505@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=dberlin@dberlin.org \
    --cc=overseers@sourceware.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).