From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Jonathan Larmour" <jifl@jifvik.org>
Cc: overseers@sourceware.org
Subject: Re: Mercurial repository
Date: Wed, 30 May 2007 16:54:00 -0000 [thread overview]
Message-ID: <4aca3dc20705300953v75eec6d2u1fea9eb125840e38@mail.gmail.com> (raw)
In-Reply-To: <465D4504.30505@jifvik.org>
On 5/30/07, Jonathan Larmour <jifl@jifvik.org> wrote:
> 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).
This was probably the script that was doing the initial mirroring of
svn to mercurial.
It took *way* longer than expected, mostly due to svn.
Anyway, i'll keep an eye out.
prev parent reply other threads:[~2007-05-30 16:54 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
2007-05-30 16:54 ` Daniel Berlin [this message]
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=4aca3dc20705300953v75eec6d2u1fea9eb125840e38@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=jifl@jifvik.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).