All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "J.H." <warthog9@kernel.org>
Cc: sedat.dilek@gmail.com, Sedat Dilek <sedat.dilek@googlemail.com>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	ftpadmin@kernel.org
Subject: Re: linux-next: Tree for December 20
Date: Tue, 21 Dec 2010 07:47:27 +1100	[thread overview]
Message-ID: <20101221074727.00900015.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4D0FA098.8000405@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]

Hi John,

On Mon, 20 Dec 2010 10:29:44 -0800 "J.H." <warthog9@kernel.org> wrote:
>
> Gingerbread released last week, loads have been spiking to well above
> 300 on the frontend machines, RAM usage has been in the ~20G range (on
> machines with 16G of RAM), and we've been running an *AVERAGE* of 2000+
> simultaneous GIT processes worldwide (normal is in the 100-200 range).
> 
> Bonus points that we blew a drive on one of the machines yesterday.
> 
> I don't think anyone was quite expecting the onslaught we have gotten
> this time around, and I'm going to have to make some changes before the
> next big release (mainly shifting Android over to the bigger machines)

Thanks for the info.  I figured something like that was up.  I guess we
all just need to be patient for a while.

> With cyclical patterns of fast and slow syncs.  We seem to be (right
> now) in the middle of one of the slow cycles with the last few syncs
> taking a couple of hours each.  The culprit, for at least the current
> sync, seems to be the box with the highest load and the blown drive,
> which I'm also reluctant to disable since it's still handling it's fair
> share of the load and dumping all of that onto the opposite US mirror
> would not be good either.

Fair enough.

I normally wait for the sync to happen before I send out the linux-next
release message each day.  I will continue to wait for a while, but will
lower my expectations :-)
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2010-12-20 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 11:46 linux-next: Tree for December 20 Sedat Dilek
2010-12-20 12:00 ` Stephen Rothwell
2010-12-20 12:12   ` Sedat Dilek
2010-12-20 18:29     ` J.H.
2010-12-20 20:47       ` Stephen Rothwell [this message]
2010-12-20 18:34   ` Chris Ball
  -- strict thread matches above, loose matches on Subject: below --
2010-12-20  9:00 Stephen Rothwell
2010-12-20 16:14 ` Zimny Lech
2010-12-20 20:49   ` Stephen Rothwell

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=20101221074727.00900015.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ftpadmin@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.com \
    --cc=warthog9@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.